And another:
sigma(17707^40)
r1=2879634038492166338098841088562260349580075078389465617426153636350133097 (pp73)
r2=9190467549312993295303242065134398381779599431651067077970666537016844201689956184044323163 (pp91)

And two more ECM results:
[code] sigma(65746047949771080612445556717533662593^10):
********** Factor found in step 2: 25564572404845320363493799567277259
Found probable prime factor of 35 digits: 25564572404845320363493799567277259
Composite cofactor 13490364891892149959464109101131011829023566834215523949255219132835401417612627753100629302338743575297000299579569196035768145660716523192417861121887977135145055329517828649825629655175602917305469062700184295612419747623223440113580818809512044378646499056107002132146255983440429429694305264194875645391360602708937169 has 323 digits

sigma(186638076777769034740323518757262489850519158739461089988974731^6):
********** Factor found in step 2: 47106710407157424426639694949
Found probable prime factor of 29 digits: 47106710407157424426639694949
Composite cofactor 618136912648522320627805638465067498000016499121435338004705928379033061183869518790776462158043417515197604544298739903203478480553569502581867517216787127446557083813879385247382071792299260066095163904679555844493516205530198012563988286733443745186733392480338283049720465878417623674358736399160507986592993393412514777418651 has 330 digits
[/code]
The numbers in t400.txt are all fairly easy SNFS targets. I've got 2 systems doing them and 1 doing ECM. ECM produces most factors per CPU day but rarely fully factors a number.

Chris K

One more:
sigma(613^66)
r1=6725596016936256922266928279844059234693217848097938425823 (pp58)
r2=1688339554941253845435607016295658783240932763399873361106382791360274115847949351469007807498461603166661271 (pp109)

And 4 ECM results:
[code] ********** Factor found in step 2: 56096506621567809010579455241939373
Found probable prime factor of 35 digits: 56096506621567809010579455241939373
Composite cofactor 1841324777712923505210730847492377935693450681412104094469031267207935384991779158027554224272691423071133821376457061959495214219162338430677983781986985726057208599251033749924477443869775086779055524535717609333937173660974002398932268147742358102489966920119717852343602104155776327759863532192141573526242038724075934270989947 has 331 digits
********** Factor found in step 2: 1166893857223708051187
Found probable prime factor of 22 digits: 1166893857223708051187
Composite cofactor 3873625221886607289705141612694210169438691821158829023230064945176833040378237991524804229313409786240103644405319720612866316351107901154097474041444370561375316143244139135807578472182743161285343144886111484704808211460968146128667024732271273079837783121703050910991819532149124456276316017519254481618176854969171943196413320884463325046385420721 has 352 digits
********** Factor found in step 2: 3950108463755251789533827587349711
Found probable prime factor of 34 digits: 3950108463755251789533827587349711
Composite cofactor 72149726486029580698844414806624164701934731374962410009447908309438997239202614625482981690402658758123390880298750029872861579808856346865651054596658551419087686938468123692660530413158981229298138425377544284159812058747275630496717831715331117873241621863819719476746538975114957380221329088863404047740928273893069823960969877765105166112787 has 347 digits
********** Factor found in step 1: 123636417041178669515958241421
Found probable prime factor of 30 digits: 123636417041178669515958241421
Composite cofactor 1167113182474150679501098918494605509354324206179369393440235231582211893061059165587910664148479070120916829132870777244113242357105677368737204221946657194751340929320236828583278381456557738084029341354837675691808487444023553483642822583134655391953613898797656475350006613416597660197136446636479206433637762050766183746896368822376081500537021257980771927128523 has 367 digits
[/code]
Chris K

At last, an ECM result with a probably prime cofactor:
[code]sigma(3333121151155141^28):
********** Factor found in step 2: 461613222739827373379870723
Found probable prime factor of 27 digits: 461613222739827373379870723
Probable prime cofactor 4068595913570254605803896745028824072553593760784651635852055305180570803147897900572282931680187674025247302158295308054647581263177629475007267787772377278181372564591030794662407156835421421589488469453508131810456365274653733851494222539271374148667024743528173936888506488394133716941286334477876005906357653060152051235799600236943440102167896888106405417423284270391391382874629659671 has 391 digits
[/code]
Chris K

[QUOTE=chris2be8;232322]At last, an ECM result with a probably prime cofactor:[/QUOTE]

Confirmed prime. Nice find. :smile:

Another from t400.txt:
sigma(3221^52)
r1=170723516314073973384153720054099820113808872827995847 (pp54)
r2=1228526936106027117209365838078812026668620881714680935212482803493224690884755802831501344866917142595207868225032899 (pp118)

And another ECM result:
[code]sigma(4833840829490268113510548333147842703698650330426092900442909241152371^6):
********** Factor found in step 2: 34314072485030723425273786903519891
Found probable prime factor of 35 digits: 34314072485030723425273786903519891
Composite cofactor 371776393255403544307046615852034198475343700326574794638359318828138643088369638267758552385773254354251784914781370539035031387188376706329842204365177589980533106756474997755561866819807014203339502654134334875488757761775558190133181004946103211733645310639466119471853859768438641542694517335314465359657045863281001229243833243369505205256455503238915010896095786617608523615447 has 384 digits
[/code]
Chris K

From t800.txt

[code]
sigma(27717270447823117430757813295399349895948507276544999762910234271693644442414393251574423728384298362215009009067958742621140986128318854312575485053375493):
Factor found in step 2: 30453960818823725899887949
Found probable prime factor of 26 digits: 30453960818823725899887949
Probable prime cofactor 288759920293341103246038563933509244288496151453106018946722089 has 63 digits[/code]

How do I run this

[code]awk '{print $NF}' t800.txt > t800.in
nohup ./ecm 3e6 < t800.in > t800_01.out &
grep 'prime factor' t*.out | awk '{print $NF}' | sort -u > factors.txt[/code]under windows? It works for linux not for windows.

[URL="http://www.lri.fr/%7Eochem/opn/"]http://www.lri.fr/~ochem/opn/[/URL]

This [code]awk '{print $NF}' < t800.txt | ecm -nn 3e6 | tee -a t800.log.1 | grep [Ff]actor[/code] also works for linux, not for windows.

[QUOTE=em99010pepe;232574]How do I run this

[code]awk '{print $NF}' t800.txt > t800.in
nohup ./ecm 3e6 < t800.in > t800_01.out &
grep 'prime factor' t*.out | awk '{print $NF}' | sort -u > factors.txt[/code]

under windows?

[url]http://www.lri.fr/~ochem/opn/[/url][/QUOTE]Carlos,

The best first step is to get a Windows port of some of the Unix utilities. I think I got GAWK from [URL="http://gnuwin32.sourceforge.net/packages/gawk.htm"]here[/URL]. It will do the filtering needed to pull all the composites out of the t* files.

Then, depending on how you start your ECM workers, you can just execute something along the lines of [code]awk "{print $NF}" t800.txt > t800.in
ECM 3e6 <t800.in >t800.out
findstr "factor" t800.out[/code]Actually, you have to adjust the command line for awk just a little....

What's the command to pull the composites out?

[code]

C:\DC\OD>awk
Usage: awk [POSIX or GNU style options] -f progfile [--] file ...
Usage: awk [POSIX or GNU style options] [--] 'program' file ...
POSIX options: GNU long options:
-f progfile --file=progfile
-F fs --field-separator=fs
-v var=val --assign=var=val
-m[fr] val
-W compat --compat
-W copyleft --copyleft
-W copyright --copyright
-W dump-variables[=file] --dump-variables[=file]
-W exec=file --exec=file
-W gen-po --gen-po
-W help --help
-W lint[=fatal] --lint[=fatal]
-W lint-old --lint-old
-W non-decimal-data --non-decimal-data
-W profile[=file] --profile[=file]
-W posix --posix
-W re-interval --re-interval
-W source=program-text --source=program-text
-W traditional --traditional
-W usage --usage
-W use-lc-numeric --use-lc-numeric
-W version --version

To report bugs, see node `Bugs' in `gawk.info', which is
section `Reporting Problems and Bugs' in the printed version.

gawk is a pattern scanning and processing language.
By default it reads standard input and writes standard output.

Examples:
gawk '{ sum += $1 }; END { print sum }' file
gawk -F: '{ print $1 }' /etc/passwd

C:\DC\OD>[/code]

EDIT: I think it is running. Thank you Frank.

[QUOTE=em99010pepe;232578]What's the command to pull the composites out?[/QUOTE]Sorry, crossed edits.....check my post above yours again.

Running SNFS against sigma(86950696619^16) I'm getting a very bad yield (less that 1 relation per special Q on average). The job file contains:
[code]n: 638115172762699546729155811851190181678421963913759319739682933573258964131966449254958965075900075177569952053993940224395304756763474267461747663348256965779826222875529
m: 657384102452686854982243639344659
c6: 1
c5: 0
c4: 0
c3: 0
c2: 0
c1: 0
c0: -86950696619
skew: 66.5598259497798
rlim: 8000000
alim: 13400000
lpbr: 28
lpba: 28
mfbr: 56
mfba: 56
rlambda: 2.5
alambda: 2.5
q0: 8000001
qintsize: 49999
#q1:8050000
[/code]
I'm taking the defaults for most of the parameters. Can anyone suggest a better set of parms for this number.

Thanks in advance.

Chris K