Print

---

Hi Mark,

Yes, it sounds that fsl_sub does not work with your cluster queueing environment. Have a search in the list, there has been some recent email exchange on patched fsl_sub versions for torque. For instance:

https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind1312&L=fsl&P=R8238&1=fsl&9=A&J=on&d=No+Match%3BMatch%3BMatches&z=4

Cheers
Stam


On 10 Dec 2013, at 21:55, Mark Postans <[log in to unmask]<mailto:[log in to unmask]>> wrote:

Hi FSL experts,

I’ve been trying to run probtrackx from the GUI, but every time I click “Go” I get the error message shown below.
Would I be right in thinking that it’s an issue with jobs not being properly submitted to our cluster?

I think I saw something similar in this previous posting: https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0710&L=fsl&P=R20397&1=fsl&9=A&J=on&d=No+Match%3BMatch%3BMatches&z=4; though there’s some discrepancy between the error message they report, and the one that I’m getting.
Do you have any suggestions for sorting this out? All help appreciated!

Thanks in advance!

Cheers
Mark Postans


 “Unable to run job: Job was rejected because job requests unknown queue "long.q".
Exiting.

Unable to run job: Job was rejected because job requests unknown queue "long.q".
Exiting.
    while executing
"exec $FSLDIR/bin/fsl_sub -q long.q ${filebase}_script.sh"
    ("probtrackx" arm line 158)
    invoked from within
"switch -- $probtrack(tool) {
                eddy_current {
                    global eddy
                     set errorStr ""
                   if { $eddy(input) == "" } { set errorStr "You need to specify..."
    (procedure "fdt:apply" line 5)
    invoked from within
"fdt:apply .fdt keep"
    invoked from within
".fdt.apply invoke"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 [list $w invoke]"
    (procedure "tk::ButtonUp" line 22)
    invoked from within
"tk::ButtonUp .fdt.apply"
    (command bound to event)”