Closed smoe closed 3 years ago
Hi Steffen,
we're only ever executing STAR (or any other tool) with the absolute fie name as specified in the configuration file in the tools section. The tools section is generated at configure time, so whichever STAR was available during the configure phase should be used for the star_map
rule.
I don't know where "genomeParameters.txt" comes into play. Annoyingly, this is not declared explicitly as an input. I wonder what generates it.
@borauyar, could you enlighten us?
STAR creates this file genomeParameters.txt
when indexing the genome under the folder star_index
. The STAR mapping requires this index folder as input. Reads the genome parameters from there. The issue could be that the STAR version that created the index is different from the STAR version that does the mapping.
Yes. That was it. Sorry. I had (previous discussion) set the limitGenomeGenerateRAM paramter for the indexing
star_index:
args: "--limitGenomeGenerateRAM 33724373088"
executable: "/usr/bin/STAR"
and set the executable with it. No idea if STAR will receive a version and path information in any near future. Since
$ STAR --version
2.7.8a
is performed with no delay, maybe it would be a neat to add this to your pipeline?
I just saw that you are presenting the full path in the "outer" logfile. Still, because of docker and chroot being confusing at times, you may nonetheless want to execute the tool for their version information only.
Yes. That was it. Sorry. I had (previous discussion) set the limitGenomeGenerateRAM paramter for the indexing
star_index: args: "--limitGenomeGenerateRAM 33724373088" executable: "/usr/bin/STAR"
That's great. I leave it to @rekado to comment on the question about versions.
Hello, I installed pigx-rnaseq now via guix as in
to help locating the cause of yesterday's "group_by" issue (https://github.com/BIMSBbioinfo/pigx_rnaseq/issues/86) but don't get as far as with my Debian package of pigx-rnaseq. The previous output directory was removed, everything else was left invariant. Here is a hick-up in the mapping that is blocking me
and the logfile of the failing process is
There could be some confusion since there are two versions of STAR on the system
I already asked to have some information on the binary that is executed in the STAR output (https://github.com/alexdobin/STAR/pull/1157). Is there something I can test/do to harden the process?
Best, Steffen