The log is more interesting for what it does not say that for what it says. factmsieve.py had just finished a batch of sieving and was about to call msieve when it wrote the last entry. I suspect anything msieve wrote to the log got lost when you reset the system.

So I can't tell why the problem occurred.

Chris K

[quote=chris2be8;217483]The log is more interesting for what it does not say that for what it says. factmsieve.py had just finished a batch of sieving and was about to call msieve when it wrote the last entry. I suspect anything msieve wrote to the log got lost when you reset the system.

So I can't tell why the problem occurred.

Chris K[/quote]
Thanks for looking. The answer was probably in the console output, but the error messages kept getting in the way and overwriting everything to be on top and I couldn't grab the console window and move it because of the error popups. I did try a copy/paste, but again the error popups wouldn't allow me to open anything to paste into.

Oh well, it's back to work on the sequence now and when I get a chance I'll try to combine some relations again.

A few thoughts did pop up:

- Could I possibly have chosen a B1 range too high compared to the B1 ranges being used by the script?

- Is there any need to combine the relations files in the order of the B1 ranges they are from?

- Is there any need to have all the B1 ranges contiguous in the relations file?

B1 is a slightly confusing term here because it almost always means the bound for ECM; I generally call the first thing lattice-sieved Q0.

The order of the relations in the msieve.dat file is not important.

[quote=fivemack;217517]B1 is a slightly confusing term here because it almost always means the bound for ECM; I generally call the first thing lattice-sieved Q0.[/quote]
And, I was kind of thinking in ECM terms - thanks for the correction.
[quote=fivemack;217517]
The order of the relations in the msieve.dat file is not important.[/quote]
I thought this, but I can't be sure of any of my thoughts anymore.:down:

Where can I find info on how the -R option (Resume) works? Thanks!

With -R option, the siever scans the output file (which must exist), determines the last processed q0 and proceeds for the rest of the range while appending to the relations file.
By Murphy's law anything that can go wrong will go wrong, so copy the output file elsewhere (because if the binary is actually old and doesn't know the -R option, it will override the file, ...and it will not resume). Also, if a user replaces the sieving side option (e.g. -r for -a), the behavior is unpredictable. Also, if the process was stuck in an infinite loop (and it does happen, rarely), then -R will happily get stuck again. So use caution. If a loop happens, don't fight it; step over the stubborn q0 by changing the -f and -c options manually. Newer binaries have patches against the inf.loop but this may happen to be a shiny new loop, never seen before. :-)

[QUOTE=Batalov;217869](which must exist)[/QUOTE]

No.

[quote=axn;217881]No.[/quote]
Even better! :smile: [COLOR=lemonchiffon](I wrote that code. Yes, it will "resume" without a file, but will it [I]really[/I] resume?)[/COLOR]

I just installed Fedora 13 on a new (to me) machine and am trying to compile ggnfs. Anyway, I get an error based on the -ltpie switch, which appears to be identified as a file.

Here's the make session. (The error is in bold. I included the entire session in case it holds more clues.):
[code]
[id@machine ggnfs]$ make pentium4
make[1]: Entering directory `/home/duser/Math/ggnfs'
echo "#define GGNFS_VERSION \"0.77.1-20060513-pentium4\"" > include/version.h
make[2]: Entering directory `/home/duser/Math/ggnfs/src'
gcc -I. -I.. -I../include -I/usr/local/include -IF:/tmp/nfs/tpie/include -DNDEBUG -O3 -ffast-math -funroll-loops -finline-functions -ftracer -fomit-frame-pointer -W -Wall -march=pentium4 -pipe -DL2_CACHE_SIZE=512 -DMALLOC_REPORTING -L/usr/local/lib -LF:/tmp/nfs/tpie/lib -o ../bin/sieve sieve.c clsieve.c getprimes.o fbmisc.o squfof.o rels.o blanczos64.o poly.o mpz_poly.o mpz_mat.o smintfact.o misc.o ecm4c.o nfmisc.o matsave.o montgomery_sqrt.o matstuff.o dickman.o fbgen.o llist.o if.o rellist.o intutils.o lasieve4/mpz-ull.o dlmalloc.o mulmod32.o lasieve4/asm/modinv1002.o makefb.o -lgmp -lm -ltpie
sieve.c: In function ‘catch_term’:
sieve.c:69: warning: unused parameter ‘sig’
sieve.c: In function ‘setDependentDefaults’:
sieve.c:91: warning: comparison between signed and unsigned integer expressions
sieve.c:95: warning: comparison between signed and unsigned integer expressions
sieve.c:95: warning: comparison between signed and unsigned integer expressions
sieve.c:99: warning: comparison between signed and unsigned integer expressions
sieve.c:103: warning: comparison between signed and unsigned integer expressions
clsieve.c: In function ‘clSieve’:
clsieve.c:237: warning: comparison between signed and unsigned integer expressions
clsieve.c:306: warning: comparison between signed and unsigned integer expressions
clsieve.c:384: warning: comparison between signed and unsigned integer expressions
clsieve.c:384: warning: signed and unsigned type in conditional expression
clsieve.c: In function ‘fillHashtableOdd’:
clsieve.c:722: warning: unused parameter ‘b’
clsieve.c: In function ‘fillHashtableEven’:
clsieve.c:802: warning: unused parameter ‘b’
clsieve.c: In function ‘fillSieve’:
clsieve.c:1110: warning: comparison between signed and unsigned integer expressions
clsieve.c:1135: warning: comparison between signed and unsigned integer expressions
clsieve.c: In function ‘add2Subblock’:
clsieve.c:1922: warning: ‘new_update.logp’ may be used uninitialized in this function
[B]/usr/bin/ld: cannot find -ltpie
collect2: ld returned 1 exit status[/B]
make[2]: *** [../bin/sieve] Error 1
make[2]: Leaving directory `/home/duser/Math/ggnfs/src'
make[1]: *** [x86common] Error 2
make[1]: Leaving directory `/home/duser/Math/ggnfs'
make: *** [pentium4] Error 2
[id@machine ggnfs]$
[/code]Here's the cpu info:
[code]
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 4
model name : Intel(R) Pentium(R) 4 CPU 2.80GHz
stepping : 1
cpu MHz : 2799.930
cache size : 1024 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe constant_tsc up pebs bts pni dtes64 monitor ds_cpl cid xtpr
bogomips : 5586.05
clflush size : 64
cache_alignment : 128
address sizes : 36 bits physical, 32 bits virtual
power management:
[/code]Here's the Linux version info:
[code]
Linux machine 2.6.33.6-147.2.4.fc13.i686 #1 SMP Fri Jul 23 17:27:40 UTC 2010 i686 i686 i386 GNU/Linux
[/code]Thanks for any insight.

Just pointing you to Jeff's page with GGNFS.

[url]http://gilchrist.ca/jeff/factoring/[/url]

[quote=em99010pepe;225077]Just pointing you to Jeff's page with GGNFS.

[URL]http://gilchrist.ca/jeff/factoring/[/URL][/quote]
Thanks,

I didn't think to check there for the error. I just searched here. I see a few messages regarding -ltpie, so I'll review those. But, it will have to wait a little bit for now. Another interruption is occurring. . .