Dear FSL Experts,
We are currently trying to start using probtrackx. All the appropriate
files appear to be present having run bedpostx. Using either a single
voxel, or a single mask and the GUI we encounter the following error
message. Probtrackx appears to write out the appropriate directory name
within which there are two files fdt_log.tcl and fdt_script.sh.
Usage: at [-V] [-q x] [-f file] [-m] time
at [-V] [-q x] [-f file] [-m] -t [[CC]YY]MMDDhhmm
at -c job [job...]
(atq | at -l) [-V] [-q x]
(atrm | at -d | at -r) [-V] [-q x] job ...
batch [-V] [-f file] [-m]
Usage: at [-V] [-q x] [-f file] [-m] time
at [-V] [-q x] [-f file] [-m] -t [[CC]YY]MMDDhhmm
at -c job [job...]
(atq | at -l) [-V] [-q x]
(atrm | at -d | at -r) [-V] [-q x] job ...
batch [-V] [-f file] [-m]
while executing
"exec batch -q long.q ${filebase}_script.sh"
("probtrackx" arm line 134)
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)
Running probtrackx from the command line with only the default options
present gives the following error:
Log directory is: ++
7
sl 0
sl 1
sl 2
sl 3
sl 4
and so on... to sl 38 followed by
run
53 53 38
Segmentation fault
Could anyone help point us in the right direction as to what may be the
problem ?
Thanks.
Mahinda
|