Alex Phillips <[EMAIL PROTECTED]> wrote
> I recently updated my E450 running Mlucas to version 2.7b, using Bill
> Rea's precompiled version from Ernst's website. I'm attempting to use the
> mlcuas.cfg file which comes in this tarball, but I get the following error
> in my pxxxxxxxx.stat file :-
>
> Restarting M(12xxxxxx ) at iteration 6484000
> WARN: radix set -1 not available - using defaults.
> Using complex FFT radices 10 32 32 32
> M( 12xxxxxx ) iteration = 6486000 clocks = 00:14:16.236.
> Res64:36B6CB8618DD551D
> WARN: radix set -1 not available - using defaults.
> Using complex FFT radices 10 32 32 32
>
> Can anyone explain what this means ?
For some reason the program is not finding, or is unable to properly read the
mlucas.cfg file. The obvious first
check (you've probably done this, but just in case) is
to make sure there's a copy of the .cfg file in the local directory from which you're
running the job. If
as i do) you're running on a multiprocessor machine
and have one master copy of the executable, plus soft
links to it in each of the various subdirectories from
which you're running jobs, there needs to be a copy of
the .cfg file in each subdirectory, obviously.
Also make sure you have read permission for the file.
Assuming you've done the above, look at the .cfg file,
preferably using an editor which shows the ^M linefeed
characters that some ftp utilities introduce into text
files. If there are any such, strip them out. (I don't
actually know if they'll cause a read problem, but it's
best to be safe.) Note that you can modify the .cfg file
while the program is running - at worst the program
won't be able to read it and will use the defaults,
i.e. you'll be no worse off than at present.
Finally, make sure the .cfg file has the proper format,
namely
# comment line 1
# comment line 2
# comment line 3
200000
# comment line 4
{FFT length 1, in K} {FFT radix set index 1}
{FFT length 2, in K} {FFT radix set index 2}
..
If all that checks out and the program still can't read
the file, do
cat *cfg
rm -f *cfg
cat>>mlucas.cfg
then paste the output of the first 'cat' into stdin and
type ctrl-d to finish input. I've had some rare cases
where my run similarly was unable to read the .cfg file,
and in the end the only thing that worked was to delete
and recreate the file - OS weirdness most likely, but
at the moment I don't remember which OS this happened
under.
Good luck,
-Ernst
p.s.:
FYI, Mlucas 2.7c (faster, of course!) will be coming out
by the end of the month (hopefully sooner, but not
later.) I'll update the timing pages by then, as well.
_________________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
