TargetFinder score cutoff seems ignored; tool always behaves as cutoff 4

Hi Galaxy team,

I am using the TargetFinder tool for plant small RNA target prediction
(Galaxy tool version: 1.7.0+galaxy1).

I may have found a possible issue with the Prediction score cutoff value parameter.

In the tool form I set the cutoff to 5. I also previously tried 5.0, but to avoid any decimal-format issue I repeated the run with the integer value 5. However, the output still appears to contain only predictions consistent with the default cutoff 4. In other words, changing the cutoff value does not seem to change the result, and the tool behaves as if the default threshold is always used.

My settings were approximately:

Galaxy instance: usegalaxy.eu
Tool: TargetFinder
Tool version: 1.7.0+galaxy1

Input small RNA sequences: mature Arabidopsis miRNAs
Target sequence database: Araport11 cDNA FASTA
Prediction score cutoff value: 5
Search reverse strand: false
Output format: tab-delimited

Expected behavior:
Predicted targets with TargetFinder scores up to and including 5 should be reported.

Observed behavior:
The output seems to be restricted to predictions with scores up to 4, as if the cutoff parameter was not passed to the underlying command or was overwritten by the default value.

Could someone please check whether the score cutoff parameter is being correctly passed by the Galaxy wrapper? Has anyone else observed similar behavior with this TargetFinder wrapper?

Many thanks!

Martin

Hi @Martin_Bartas

Interesting result. I couldn’t find that this is a known. Would you like to share back an example to review closer? FAQ: Sharing your History. You can post the link back here or in a direct message (let me know if you can’t start one up!).

Meanwhile, I’ll also try to test to see if I can trigger this use case. More soon.

Thanks for asking about this! :slight_smile:

Hi @jennaj,

Thank you very much for your prompt answer! :slight_smile:

I am enclosing 2 screenshots from my history; it is clearly visible that the output is the same, regardless of the cutoff. The cutoff of 5 is much more relaxed (in comparison to the default strict cutoff of 4), and should produce many more hits. Nonetheless, in both cases, I received exactly the same number of 41,078 hits.

Thank you once again for your time and willingness to help!

Best wishes,

Martin

Hi @Martin_Bartas

Apologies for the delays! Our team is at our annual conference throughout this week but let’s keep going with the review for this tool.

For your runs, I would like to look at the details closer (command line, job container). This will allow me to troubleshoot with the correct developers. I am going to message you direct here so you don’t have to share the history publically.