Yafu

[bsquared]

It probably doesn't like the space in your directory name. Try renaming (and changing the yafu.ini file to match) to gnfs_executables.

p.s.
You should use yafu-32k-Win32.exe on a core2... it will be faster. And if it is a 64 bit version of winXP you should definately use yafu-32k-x64.exe.

p.p.s
Thanks for your comments!

[mnh001]

Ok, I'll give that a try. And now you mention it, ya I probably do have the 32 bit version.

I'll let you know how it goes.

[mnh001]

Ok, took out the space in the directory name but it still crashed saying it couldn't find
the file gnfs-lasieve4I12e.exe. :(

And I used yafu-32k-Win32.exe this time.

Also this is what the ini looks like:

B1pm1=100000
B1pp1=20000
B1ecm=11000
rhomax=1000
threads=1
%ggnfs_dir=..\ggnfsexecutables\ggnfs\
ggnfs_dir=../ggnfsexecutables/ggnfs/
tune_info=Intel(R) Xeon(R) CPU X5460 @ 3.16GHz,LINUX64,2.18911e-05,0.202416,0.389149,0.100747,96.2505,3158.64
tune_info=Intel(R) Xeon(R) CPU X5570 @ 2.93GHz,LINUX64,2.42568e-05,0.200833,0.451996,0.0988934,96.4564,2926.14ecm_qs_ratio=0.25
ecm_gnfs_ratio=0.25


Is this ok?

[bsquared]

Windows requires the slashes to go the other way... i.e. you should use this line:

ggnfs_dir=..\ggnfsexecutables\ggnfs\

You can get rid of the other one.

Also, just to clarify, the 32k version will only make YAFU's siqs routine faster - it won't help ggnfs at all.

cheers,
- b.

[mnh001]

Ok, I'll try again. Thanks. Let you know...

[mnh001]

Oh also, do I need to keep those tune statements in the ini?
They concern Linux and I have Windows.

[mnh001]

I took out the extra line in the ini and made sure the slashes were correct in the other
but it still crashed for the same reason. I'll keep playing with it, see what I can do. It
just seems odd for such a clear cut command not to work.

[mnh001]

I got it to work partially. Instead of the short version of the path I put in the full path in the ini file.
It then ran a whole lot of poly tests then crashed again. This time it said:

04/02/11 20:50:57 v1.24 @ HOME, nfs: commencing gnfs on c100: 1018979337456225035714934025075344288205054863323166920696334625238968374307490538496140762051312209
04/02/11 20:50:57 v1.24 @ HOME, nfs: commencing msieve poly select
04/02/11 21:11:03 v1.24 @ HOME, nfs: commencing lattice sieving with 1 threads
04/02/11 21:11:05 v1.24 @ HOME, could not open rels0.dat for reading

I've looked thru the directories and can't find rels0.dat anywhere. Is it supposed to be part of the package or does it get created during runtime? Thanks.

[bsquared]

Originally Posted by mnh001

I got it to work partially. Instead of the short version of the path I put in the full path in the ini file.
It then ran a whole lot of poly tests then crashed again. This time it said:

04/02/11 20:50:57 v1.24 @ HOME, nfs: commencing gnfs on c100: 1018979337456225035714934025075344288205054863323166920696334625238968374307490538496140762051312209
04/02/11 20:50:57 v1.24 @ HOME, nfs: commencing msieve poly select
04/02/11 21:11:03 v1.24 @ HOME, nfs: commencing lattice sieving with 1 threads
04/02/11 21:11:05 v1.24 @ HOME, could not open rels0.dat for reading

I've looked thru the directories and can't find rels0.dat anywhere. Is it supposed to be part of the package or does it get created during runtime? Thanks.

That file gets created by gnfs-lasieve4I*e. Since it didn't get created, and since the lattice siever "finished" sieving in 2 seconds (according to the log entries), I would guess that something is wrong with the siever (i.e., it aborted with an error). Do you know for sure that it runs on your system? If you've independently tested the ggnfs binaries and they work, then I would need to see the ggnfs.job file that yafu created to try to understand what's going on.

[mnh001]

If you mean by independently tested, trying to run each of the exe's by themselves,
yes I've tried that and they all give the message "not a valid Win32 application".

Does this mean I won't be able to use the most powerful parts of the program? That would be a real bummer. I thought that finally I was going to get to use something
with real power.

At least it has worked on smaller numbers (65-95 digit) before I tried this 100 digit
one. Hey wait, this is the Windows version I have. It is supposed to work, right?

There was no ggnfs.job file created.

[Brian Gladman]

Are you sure that you are not using 64-bit ggnfs binaries by mistake?