You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
as you can see, the STAR index was manually generated with STAR in a separated folder and not with RSEM.
The problem I'm facing is that the pipeline is calling STAR with the path to the rsem_index in place of the proper one.
I think tha this is happening because with the option --aligner 'star_rsem' STAR is not called directly but through the RSEM function rsem-calculate-expression thus ignoring the --star_index argument
Expected behaviour
I'm aware that the simple fix is to generate the star index together with the RSEM one with the rsem-prepare-reference function but I think it would be worth adding a warning in case someone tries to specify the STAR index with the --aligner 'star_rsem' option
Hi @ftucos ! Well spotted and apologies for the inconvenience! Yes, the pipeline has a number of workarounds to deal with STAR indices at the moment. The main reason I implemented things in this way is because we have to support an older version of STAR in this pipeline for legacy purposes in order to support the AWS iGenomes references we provide as standard (see footnote here). However, because we don't have any RSEM indices on AWS iGenomes we can use the latest version of STAR with that and so I added functionality to that module to build the entire index including the STAR files (see #511). In any case, for the purposes of simplicity with the Nextflow implementation I would suggest that the STAR and RSEM indices are placed in the same folder and provided via --rsem_index
Hi @ftucos. As you suggested, the pipeline will now generate a warning when --aligner star_rsem, --rsem_index and --star_index are provided together. Thanks for reporting!
Description of the bug
In my pipeline I specified the path to both the STAR and the RSEM index, since they were generated independently
This is how the command looks like:
as you can see, the STAR index was manually generated with STAR in a separated folder and not with RSEM.
The problem I'm facing is that the pipeline is calling STAR with the path to the rsem_index in place of the proper one.
I think tha this is happening because with the option
--aligner 'star_rsem'
STAR is not called directly but through the RSEM functionrsem-calculate-expression
thus ignoring the--star_index
argumentExpected behaviour
I'm aware that the simple fix is to generate the star index together with the RSEM one with the
rsem-prepare-reference
function but I think it would be worth adding a warning in case someone tries to specify the STAR index with the--aligner 'star_rsem'
optionLog files
System
Nextflow Installation
Container engine
The text was updated successfully, but these errors were encountered: