On Tue, Sep 20, 2011 at 15:00, Bruce Fischl <fischl(a)nmr.mgh.harvard.edu>
wrote:
> what other information would you like? Can you remind me: are you running
> on a cluster? Does this happen if you run on your local workstation? Do you
> have limits on # of open files?
Yes, I am running on a cluster with Gentoo (Linux imageserver1
2.6.20-gentoo-r8 #2 SMP Fri May 25 10:23:59 CEST 2007 x86_64 Intel(R)
Xeon(R) CPU X5355 @ 2.66GHz GenuineIntel GNU/Linux)
I runs without problems on the same data on a MAC
The limits in the cluster are:
ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 155648
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 155648
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Still haven't resolved the problem. I was wondering, is there some way of
forcing mri_ca_register to finish fast (to make error tracing easier)? I
have tried using -tol [some large numer], but still it takes many hours
before reaching the part where talairach.m3z is written (the part that fails).
Best,
Lauge