[QUOTE=akruppa;298832]Sweet. Thanks for helping this along.[/QUOTE]:geek:

i3250 was even sweeter:[code] c130 = 2^2 * 965790972696315384966086853945791114057779457459931899639792547143707488146567493083304434873606920192324847235556269383685858089[/code]There's still good things happening for this one!

:party:

p39... p33... c95... c104...

So who did the deed after bsquared stopped?

line 3267:
[code]Using B1=4000000, B2=11415205630, polynomial Dickson(12), sigma=14220810860951883440
Step 1 took 8874ms
Step 2 took 6116ms
********** Factor found in step 2: 108909075340171324033834877863247334250507
Found probable prime factor of 42 digits: 108909075340171324033834877863247334250507
Probable prime cofactor 177864168042791473550628769400005983592699829761569883028664427 has 63 digits
[/code]

Ach. Lost the driver again.

You just had to...
Well, there we go.

[QUOTE=schickel;298889]So who did the deed after bsquared stopped?[/QUOTE]
Beware! Downdriver hunters in sight! :smile:

(not me! I have no contribution to this sequence up to now, but I was thinking to reserve it when it will reach 83 digits and get some 2^3*3*5 driver, and the people/poachers will lose the interest... to grab it for myself and bring it back to 150 digits :smile:)

(edit: hopefully by then I could free 3-4 cores...:whistle:)

[QUOTE=LaurV;298894]... to grab it for myself and bring it back to 150 digits :smile:)

[/QUOTE]

Wrong direction. Better lose a 2 and stay at 3^0... :wink:

So, has the C114 been fully ECMd, or did whoever was running the sequence give up on it?

Looks like everyone was just hoping for an ECM factor. I start NFS.

[QUOTE=akruppa;298918]Looks like everyone was just hoping for an ECM factor. I start NFS.[/QUOTE]

Actually, I just came back from a meeting to notice that by accident I had left the computer running ECM on the number (I was hoping to get a lucky hit with a few curves). I ran 3k@3e6 + 1k@11e6... so yes, it should be ready for NFS.

Done. This was the first NFS factorization I've done in weeks that didn't get pre-empted by someone else. :smile:

Edit: 2^4? :huh:

Edit: did p40 on i3301 c123. Edit: And another 2400@11M.

C123=3 (mod 4)
C123=2 (mod 3)
C123=4 (mod 7)
C123=19 (mod 31)

:smile:

I did 2400 curves @ B1=4e6, B2=11415205630 on line 3301 c123. NF

Starting NFS. But feel free to beat me if you can.

[QUOTE=jrk;299020]Starting NFS. But feel free to beat me if you can.[/QUOTE]
460026165306479598516699250975582732510116389920830649494169

But looks like someone did beat me afterall. :smile:

i3307 c118 now. I did 300@3M so far. Others probably did a lot at 3M as well so I switch to 11M for now. Is anyone doing NFS already? If not I can take a shot at it.

[QUOTE=akruppa;299050]i3307 c118 now. I did 300@3M so far. Others probably did a lot at 3M as well so I switch to 11M for now. Is anyone doing NFS already? If not I can take a shot at it.[/QUOTE]

I don't know who has factored it - it is now at i3309 with a c95.

[QUOTE=Andi47;299053]I don't know who has factored it - it is now at i3309 with a c95.[/QUOTE]

I just looked it up myself it's now at 3316 with a C100 as a cofactor.

Back to 2^3

line 3318 c112:
[code]prp55 factor: 7090081195318016549333815793374533246963041294567435917
prp57 factor: 148569087309806143812250107634564281066384622365315363329
[/code]

.

Not bad!

[QUOTE=akruppa;299078].[/QUOTE]

Love it!

Out of curiosity, what program does "everybody" (apparently except me) use to run 2k+ ECM curves?

I use YAFU, [strike]which is really just an extra layer of code on top of[/strike] what akruppa said. Just use [URL="http://ecm.gforge.inria.fr/"]GMP-ECM[/URL], which is what everyone else uses.

YAFU is rather more than that but one of the things it can do is execute GMP-ECM for you.

I did the c116 on line 3328 (by NFS, via yafu), now working on the c116 of line 3330.

the DB is down :(
Edit:up

[QUOTE=c10ck3r;299100]the DB is down :([/QUOTE]

Up for me.

This graphic looks wonderful and amazing. It is going down so slowly, walking on tiptoes, like it is afraid of something, but still goes down. In my language we have an expression for it, how would you say in English when someone fart, but without any sound? Is it "sing"? (not like in singing a song, but like the air going out from a low pressurized pipe, without whistling). Or whisper? Like in the joke with blondes "what is this smell?", "sorry, I could control the noise, but couldn't control the smell...". This sequence is whispering its way down... Or this is a sung walk down (?!)

[QUOTE=LaurV;299110]how would you say in English when someone fart, but without any sound? [/QUOTE]

Silent but deadly.


The silent fart is not a thing of poetry, but a thing for which to don masks.

a.k.a SBD
:explode:

[ATTACH]7976[/ATTACH]

[QUOTE=Batalov;299181][ATTACH]7976[/ATTACH][/QUOTE]

You know somethin' the DB don't?

[CODE]Could not connect to database[/CODE]
Dilbert-from-the-future told you! Too many lurkers, you know. ;-)

:rant:

At least we haven't caught a bad driver (yet).

:doh!:

Future Dilbert was trying to tell us something...

[QUOTE=bsquared;299193]:doh!:

Future Dilbert was trying to tell us something...[/QUOTE]

Now we're at a 2^3 * 5 [URL="http://www.mersenneforum.org/showpost.php?p=174259&postcount=20"]guide[/URL].

[QUOTE=Dubslow;299196]Now we're at a 2^3 * 5 [URL="http://www.mersenneforum.org/showpost.php?p=174259&postcount=20"]guide[/URL].[/QUOTE]
Whelp, we've escaped that, and along the way, ran across a 37^2 on line 3407. In the meantime, the DB has been conked out the last half hour or so, and it's [URL="http://www.downforeveryoneorjustme.com/factordb.com"]not just me[/URL].

Last I knew, we were at 3409:
2^3 · 937 · 7465504451<10> · 7318948406...61<102>
and my NFS just split the last one as
PRP57 = 198903918149090283322980891107642787318192482464665037007
PRP46 = 3679640137302425458160910470228581063166538023
and now I want to go watch a baseball game. So, if/when the DB fixes itself, that's where we left off.

Whelp
 

Since FDB still appears to be down, if no one complains in the next 20 minutes or so, I'll pick it up where I left it and run aliqueit overnight; if the DB is back by tomorrow (1600-1900 UTC or so) I'll upload the work and go back to regular work continue as usual.

I have about +43 iters from your point


...nothing good, dude. ;-]

...not too bad. Put in the 2^2*3 thread. Maybe someone will pick it out of the three hundred sequences there. :-)

[QUOTE=Batalov;299226]I have about +43 iters from your point[/QUOTE]Gee, just over the 20 minute mark.....any good news to share?

[QUOTE=Batalov;299226]I have about +43 iters from your point


...nothing good, dude. ;-][/QUOTE]

[QUOTE=schickel;299227]Gee, just over the 20 minute mark.....any good news to share?[/QUOTE]
Well I didn't check until now; but, judging by the edit he made after you posted, not good news. We got us an updriver?

Edit: Damn edits.

Iteration +59 = 2^2 * 3^2 * p
Iteration +60 = 2 * ...
:fusion:



P.S. That _is_ rare, Tom is my witness!

That calls for a song:
[YOUTUBE]K8BnVqqY-I4[/YOUTUBE]

Wow, that was a hell of a drop :smile:

In other news, instead of just timing out of the DB, I get a "Connection refused", so at least somebody is doing something there.

[QUOTE=Dubslow;299232]Wow, that was a hell of a drop :smile:

In other news, instead of just timing out of the DB, I get a "Connection refused", so at least somebody is doing something there.[/QUOTE]

I have emailed Syd in the morning and he answered that it seems to be a hardware problem - he has informed the provider and they are working on it.

What is being meant by
[CODE]insert into U values(1100000000508647107,"BZh41AY&SY¶ä=¼\0\05\0à \0uO0)ž™2$ÃJŠK àv–>ŽÐVK«}±M²† ãÕœ$0ÑT,ïŠäµç>ôX.\n*ji–VYâQ#ø»’)„…·!íà",116,4125058366) - Duplicate entry '1100000000508647107' for key 'PRIMARY'[/CODE]
whatever which I get that way is being the following, the follows, as such, away

By the same way,
id1100000000508647107 =
[CODE]89061363102028401121970356170035861240390590751041341095318236415188850592661162942318064938811849202657831014377534
[/CODE]
The factorDB problem seems to be with querying with the following
(above mentioned) number only, actually
So, thus
thereby what iteration from the aliquot sequence (314718) is being the
(this) number itself, rather
c116 = id1100000000508647107


[QUOTE=schickel;298757]Was that on purpose?[/QUOTE]
What lasted for only 3 lines - "Batalov" had actually called it to be a suspense. To keep it a mystery furthermore, I put it into the multiple nested code boxes, as such. The fact is being that following it,
you should have quite directly, automatically known to have scrolled down that code boxes already,

@ Batalov - "Creyaufmüller" hasn't received your result from the sequence 345324" rather

By the way,the fact that
[I]314718 > i10000 [/I] the same thing
is being [I]true[/I]?
by now itself

For the other numbers, aliquot sequences
the factorDB works out to be fine enough for me
although

Let alone for the sequence this aliquot 314718,
that factorDB is being a problem Alone solely
mainly due to the value for
c116 = id1100000000508647107
due to a duplicate entry from the occurrences from the "unique" Primary Key field

For the following number, aliquot sequence 9298091736
has escaped from a 2*3 driver, factor out number
9298091736 completely in order to know about
the secret behind this number, the around this fact

98415 = 5*3[sup]9[/sup]
972 = 4*3[sup]5[/sup]
9565938 = 6*3[sup]13[/sup]
94143178827 = 9*3[sup]21[/sup]
9298091736 = 8*3[sup]19[/sup]
903981141 = 7*3[sup]17[/sup]

98415 = 98304 + 111
98415 = 5*3[sup]9[/sup]; 98304 = 3*2[sup]15[/sup]

2[B]48965[/B] * 3 = 7[B]46895
[/B]

Even if the sequence is currently broken in the DB, we could continue putting the factors there by starting beyond the breaking-point; for example from [URL="http://factordb.com/sequences.php?se=1&aq=40957875574394316311003047843043516950271720473684192538168111457395057835508589937432267551919865595270070289148056&action=last20&fr=0&to=100"]this iteration[/URL]. (I hope I got the right number to start from..)

So, how about it, Batalov. :whistle:

I'll just attach what I have.
Good progress, so far.
Last line is
[CODE] 1079 . 264453232670284331976633901625664441371708292876721152867259248247954468163837758665058640482771590876708963935296954 = 2 * 7 * 10729 * 777943193 * 2263151951569827617532564242722039084172616978774700396532383771656314128890021895862518392282885307963
[/CODE]
(I started from "i1000")

I went to bed at [URL="http://factordb.com/index.php?id=1100000000508711196"]c118[/URL], now it is done and [URL="http://factordb.com/sequences.php?se=1&aq=40957875574394316311003047843043516950271720473684192538168111457395057835508589937432267551919865595270070289148056&action=last20&fr=0&to=100"]going, going[/URL] (c111 is in NFS in 12 threads).

[COLOR=green]P.S. I just hope that we are not advancing a random 120-digit sequence (due to a before-crash bug in the database - it's a possibility). Can someone stitch both sequences in their local file and verify with aliqueit from start to (current)?[/COLOR]

[QUOTE=Batalov;299252]
[COLOR=green]P.S. I just hope that we are not advancing a random 120-digit sequence (due to a before-crash bug in the database - it's a possibility). Can someone stitch both sequences in their local file and verify with aliqueit from start to (current)?[/COLOR][/QUOTE]
I don't have a local copy of the pre-crash elf file, but I'm pretty sure the "starting" number in the link you gave is the one I did NFS on, so unless your computer is wrong, then it's the right sequence.

[QUOTE=Dubslow;299253]I don't have a local copy of the pre-crash elf file, but I'm pretty sure the "starting" number in the link you gave is the one I did NFS on, so unless your computer is wrong, then it's the right sequence.[/QUOTE]

Hi,

This was being certainly the last number that I had seen just
simply before the factorDB crash point

314718: i9869
=
89061363102028401121970356170035861240390590751041341095318236415188850592661162942318064938811849202657831014377534 = 2 * c116

that number which was being stored from into my own PC system, as such, as since, as
as at last, lately

Another c116 now
[CODE][May 12 2012, 10:54:03] *** Starting 4788:1081 = 134967575610652164973483175954455896178722111445564935398464106286937706938528018196106390327198694023210954166979386 (117 digits)
[May 12 2012, 10:54:23] *** Starting 4788:1082 = 67483787805326082486741593864234848177246906042350046753511070557833596517544925020993698736134351323477632015583014 (116 digits)
[May 12 2012, 10:54:39] *** Starting 4788:1083 = 36244087911903198421907983623916714698502720700390629876961169033416195563145490389801396058076787023892591447349466 (116 digits)
[/CODE]

I have attached my local copy from end of april - last line in this copy is 4788:3125

edit: unfortunately my local copy seems to be too old to be stitched to Batalov's file.

My most recent copy ends at line 3258: [url=http://jaysonking.com/aq/4788.elf.bz2]4788.elf.bz2[/url]

[QUOTE=jrk;299260]My most recent copy ends at line 3258: [url=http://jaysonking.com/aq/4788.elf.bz2]4788.elf.bz2[/url][/QUOTE]

Thanks!

It seems we need still a few more iterations to stitch it to Batalov's file.

[QUOTE="factordb.com"]Offline to repair sequence table[/QUOTE]

'M-kay, then.

Anyone - if someone has some of the missing lines between 3258 and ¿3409? - please post them.

I found a snapshot up to 3355 in my files (May 11).


@Andi: "Does it fit to the file you posted before?" There's still a gap of 50+ lines, but it is smaller now.

c116 is in algebra... ETA 5 min

[QUOTE=Andi47;299265]Anyone - if someone has some of the missing lines between 3258 and ¿3409? - please post them.[/QUOTE]

if you know a node you can look at the node graph still, unless it got corrupted.

[QUOTE=Batalov;299266]I found a snapshot up to 3355 in my files (May 11)[/QUOTE]

Does it fit to the file you posted before?

Someone could try aliqueit copying in the factors from the db. Could be a little painful but only necessary for >~25 digits.

[QUOTE=henryzz;299269]Someone could try aliqueit copying in the factors from the db. Could be a little painful but only necessary for >~25 digits.[/QUOTE]
[URL="http://factordb.com/index.php"][COLOR=#800080]http://factordb.com/index.php[/COLOR][/URL] => "Offline to repair sequence table"

How can you insert factors when the webinterface is detached from the backend, dude?

[URL]http://factordb.com/result.php[/URL]
[URL]http://factordb.com/report.php[/URL]
[URL]http://factordb.com/sequences.php?se=1&aq=40957875574394316311003047843043516950271720473684192538168111457395057835508589937432267551919865595270070289148056&action=last20&fr=0&to=100[/URL]

...so you think it is a good thought to insert into a database that is being repaired? You will be inserting into "[URL="http://en.wikipedia.org/wiki/Write-only_memory"]write-only memory[/URL]" :-)
If Syd made his DB conventionally, then there are (at least) two instances, production and test (which will be flipped when one is repaired and then sync'd).

Inserted a few more lines, but don't be surprised when they will be gone after the database repair.

P.S. And there, Syd figured that he left a door open for you. It is now shut.

Anyway, it is line +101, a c95.
In line +109, a c109. Running NFS.

+129 size 106
+137 dodged
+153 size 103 still going down
+161 size 101
+174 size 99

+194 size 93 gnfs-90 (maybe the last one? :rolleyes:)
+205 size 91 siqs-89 (to please Ben)
+216 went under size 90... [SIZE=1]Now I can sit back and simply watch. (Before I was firing parallel ecm helpers)[/SIZE]
went under size 70... quite a view
went to size 33, bounced a few times
acquired [COLOR=darkred]2^4 * 31 (with some 3's)[/COLOR]
[COLOR=black]back to size 102 and climbing[/COLOR]

[QUOTE=Batalov;299284]+194 size 93 gnfs-90 (maybe the last one? :rolleyes:)[/QUOTE]

Why are you doing gnfs on a c90?

Because it takes equal amount of time, maybe slightly faster by gnfs.

Do whatever is faster for you - it just surprises me that c90 is faster by gnfs. For me on intel chips, the crossover is more like c95, even with asm ggnfs.

Passed the low point of c33 and now climbing.
Here are some datapoints (maybe someone can whip their C30_C90 database or something):
[CODE] 1520 . 7877849472767552998597128164446042 = 2 * 29^2 * 4683620376199496431984023878981
1521 . 4360450570241731178177126231333924 = 2^2 * 11 * 651289 * 152161558576416473477879539
1522 . 3964058754517948762781159679620476 = 2^2 * 13^2 * 83 * 1549 * 1186657513 * 38436026453915081
1523 . 3643126475221070039719491285937124 = 2^2 * 8237 * 18289471 * 6045664560420971483203
1524 . 2733119209091669900766551773318684 = 2^2 * 7130924791 * 83976068711 * 1141030327271
1525 . 2049839407550635113080940229186532 = 2^2 * 393143 * 1303494789142013919286964431
1526 . 1537388680126500328908140183392924 = 2^2 * 17 * 73 * 309707630968271621456112043391
1527 . 1350325271021664269548648509194084 = 2^2 * 11 * 59 * 7573 * 16189969 * 45433049 * 93378705733
1528 . 1271607936900717275983981948245916 = 2^2 * 419 * 1008863 * 752050528966493876457907
1529 . 959019175373726185861780887499364 = 2^2 * 1217 * 32497 * 6062244538227434797544809
1530 . 720695101552539005145730505350516 = 2^2 * 97 * 1857461601939533518416831199357
1531 . 553523557377980988488215697409072 = 2^4 * 3^5 * 859189 * 12051663251 * 13749096375071
1532 . 1052949460001452511417370546825168 = 2^4 * 3^3 * 1054813 * 6070901 * 13460717 * 28276585219
1533 . 1969409059265479394126544926026032 = 2^4 * 3^2 * 7^2 * 23 * 59 * 789212737 * 260617410851612183
1534 . 4834208698650298478456082305700048 = 2^4 * 3^2 * 11 * 1499 * 40851099069037 * 49838485907569
1535 . 9934622837192968750778912999939952 = 2^4 * 3^2 * 7 * 2857 * 3449694303184940063245840417
...
2229 . 115363930459598115076585803700262248604756269457724703948880263626885731587453545112645488 = 2^4 * 3^3 * 31 * 107 * 11887 * 2823109293041057 * 2399058683596978427352348904766698736402360051659166426029709903
2230 . 229678717793684879936003563841485114486569525337977146601057127276710853487961061932945552 = 2^4 * 3^3 * 31 * 149 * 9337 * 81619 * 26548790440813 * 700447553024804114911387 * 8122132232403516941125145344725226733
2231 . 455499897867063568213677526596679939683252624284465149639001438767236013693135296405614448 = 2^4 * 3^4 * 31 * 487 * 4244137 * 2417789384215678643 * 6833827868831380383121159783 * 331986734848973377007462499643
2232 . 908171068571533734727211252285005460143137721608575840796598884364701095613204628581273744 = 2^4 * 3 * 31 * 37 * 564197 * 16414187 * 10438343243 * 170640173592810885779548210313068522158945175261817226039905837
2233 . 1579076778561714268485683889867895818097388869039046817555343844849066206229329523940913008 = 2^4 * 3 * 17^2 * 31 * 113 * 113153 * 1888069 * 11352251 * 65716252540401168033897866281 * 203885021023842219181217860023600589
2234 . 2933691419398671309968264510568285846375435394409480435228685764446742893444789907033346192 = 2^4 * 3 * 7 * 31 * 59 * 4773769525694940166966506076974611820106347786992437376703190926030915432328344116993
2235 . 6158620970020939529642821623880638810671918854607795489935279800908779875585067431958105968 = 2^4 * 3 * 31 * 6084708800570447 * 30372344410344440407 * 22395585992260967394502546204248924968947809786197659
2236 . 10264368283368235249004622204210731944286506456223584376319291181890268935828764949283319952 = 2^4 * 3 * 13 * 31 * 41 * 53 * 59 * 4138797752330330190487534286923093158439284551051838665864869978499228804738791519
2237 . 21022940208344573484121771516338467464120705486291135015999033796873503761131614125027643248 = 2^4 * 3 * 19 * 31 * 16190159303 * 45928874278950316260854251896564103529383408201248593955096181836677274762503
2238 . 37988821783635986846365961417458974988483830152372339321305482821153115225587296093349818512 = 2^4 * 3 * 31 * 1621 * 290189 * 2215651 * 10975949137 * 36367576697 * 707690427011941 * 86713718227204808774053865709539683979[/CODE]

[QUOTE=10metreh;165862]I hope I live to see it reach 10000 lines![/QUOTE]

Your wish is granted.

[QUOTE=Batalov;299288]Passed the low point of c33 and now climbing.
Here are some datapoints (maybe someone can whip their C30_C90 database or something):
[CODE] 1520 . 7877849472767552998597128164446042 = 2 * 29^2 * 4683620376199496431984023878981
/Snip/
2238 . 37988821783635986846365961417458974988483830152372339321305482821153115225587296093349818512 = 2^4 * 3 * 31 * 1621 * 290189 * 2215651 * 10975949137 * 36367576697 * 707690427011941 * 86713718227204808774053865709539683979[/CODE][/QUOTE]
I'm updating the db by running these 2 alq seqs (longer by yafu, shorter by dario's website)

Why on earth would you want to do that?

The [URL="http://factordb.com/sequences.php?se=1&aq=40957875574394316311003047843043516950271720473684192538168111457395057835508589937432267551919865595270070289148056&action=last20&fr=0&to=100"]links above[/URL] are already [URL="http://factordb.com/aliquot.php?type=1&aq=1100000000508692618"]populated[/URL] - you will simply be heating up your place.

Gah!
 

So much happened while I was gone! So close! 33 digits... dang. How easy is it to escape 2^4*31?

[QUOTE=Batalov;299186][CODE]Could not connect to database[/CODE]
Dilbert-from-the-future told you! Too many lurkers, you know. ;-)[/QUOTE]
Dilbert-from-the-future couldn't be wrong, now, could he?

[QUOTE=Batalov;299266]I found a snapshot up to 3355 in my files (May 11).


@Andi: "Does it fit to the file you posted before?" There's still a gap of 50+ lines, but it is smaller now.

c116 is in algebra... ETA 5 min[/QUOTE]

can you please post the lines between lines 3256 and 3355? The database is still erroring out on sequence 4788.

I cannot. Syd needs to do some deletions that his database says to do (the tables are read only -- ...that means for the mortals; of course he can write):
[QUOTE]delete from CF where fid=1100000000508647107 - Table 'CF1' is read only[/QUOTE]

[QUOTE=Batalov;299305]I cannot. Syd needs to do some deletions that his database says to do (the tables are read only -- ...that means for the mortals; of course he can write):[/QUOTE]

I thought you had a snapshot up to line 3355... sounded like it was a local copy. Did I misunderstand something?

[QUOTE=Andi47;299308]I thought you had a snapshot up to line 3355... sounded like it was a local copy. Did I misunderstand something?[/QUOTE]

I think he misunderstood you wanting him to attach those lines to the forum.


(Out of context, that sentence is a long load of crap.)

If we attach every fart we make to the forum, it will indeed smell not so well very soon (and will look like the OPN gratutious factor thread), but, hell, why not.
Your wish is my command.

[QUOTE=Batalov;299310]If we attach every fart we make to the forum, it will indeed smell not so well very soon (and will look like the OPN gratutious factor thread), but, hell, why not.
Your wish is my command.[/QUOTE]

Thanks!

This is not about attaching every fart, but about trying to reconstruct / collect the missing parts to stitch the parts together. We don't know when (and to what extent complete) the sequence will be back in the database again...

I can kinda agree with that. [I]Even though[/I] my own estimate that this will be very soon and doesn't warrant ...ehm... (I've already been rude, so I'll try to choose words more temperantly) ... ok, I'll call this hoarding.

Like not throwing away credit card receipts (worse yet, make copies of these) -- because there could be a mistake in billing. On one hand, yes, true, this can happen and did happen on my memory once or twice in ten years. On the other hand, one's home starts looking like a pawn shop or a dashboard of some cars.

I think we should boldly trust the database.

P.S. Clarification: I mean, we should have some diligent footprints of our computations stored somewhere in own archives (e.g. I believe that I have > 10[sup]4[/sup] ggnfs.logs and polys for hundreds of aliquot sequences, and dozens of memorable C/Hom.C./etc snfs polys, again e.g. my beloved octics); -- just not on the forum. Especially when the results are already in FactorDB and/or near-repunits, Cunn. logs, NFS @ Home records etc

[QUOTE=Batalov;299316]IP.S. Clarification: I mean, we should have some diligent footprints of our computations stored somewhere in own archives (e.g. I believe that I have > 10[sup]4[/sup] ggnfs.logs and polys for hundreds of aliquot sequences, and dozens of memorable C/Hom.C./etc snfs polys, again e.g. my beloved octics); -- just not on the forum. Especially when the results are already in FactorDB and/or near-repunits, Cunn. logs, NFS @ Home records etc[/QUOTE]
Well, how about if we delete the attachments (at least, maybe the messagess too?) after the DB problems are cleaned up?

The future Dilbert says that they've already had been deleted.
Ah wait, it is still May of 2012; he is sometimes confused. ;-)

[QUOTE=Prime95;299289]Your wish is granted.[/QUOTE]Of course, this is a little less exciting since 933436 happened.....[code]933436 12428. sz 166 2^2 * 5^3 * 7 * 13 * 23 * 89 * 433 * 443[/code]

[QUOTE=Batalov;299316]I think we should boldly trust the database.[/QUOTE]As someone once said, "Trust but verify".

[COLOR="White"]I'm keeping a local copy of all the sequences "just in case".....[/COLOR]

It is a Russian proverb, yes. (You-know-who picked it from the Russians.)

The DB now shows i3363: c116 = 2 * c116. Anyone with more iterations to put there? :smile:

[QUOTE=Raman;299255]Hi,

This was being certainly the last number that I had seen just
simply before the factorDB crash point

314718: i9869
=
89061363102028401121970356170035861240390590751041341095318236415188850592661162942318064938811849202657831014377534 = 2 * c116

that number which was being stored from into my own PC system, as such, as since, as
as at last, lately[/QUOTE]

This was being the last number that I had seen line, the thing that I had been written much before.

It should have been 314718: i9823 NOT i9869 at all

The lines corresponding to 314718: i9823 THROUGH i9869 are being missing out

314718: i9823 would seem to have been corrupted within the factor database meanwhile

Does that mean the lines following i9823 would mutate leading to wrong subsequent result iterations,
incorrect values for the lines beyond the line 314718: i9823 which is being after the following line
that is being given away into
id1100000000508647107 -> id1100000000508756358 = 2*c116

[QUOTE=rajula;299333]The DB now shows i3363: c116 = 2 * c116. Anyone with more iterations to put there? :smile:[/QUOTE]

still not stitchible to the file Batalov posted here yesterday. I guess there are still ~40-50 iterations missing.

[QUOTE=rajula;299333]The DB now shows i3363: c116 = 2 * c116. Anyone with more iterations to put there? :smile:[/QUOTE]

[QUOTE=Andi47;299341]still not stitchible to the file Batalov posted here yesterday. I guess there are still ~40-50 iterations missing.[/QUOTE]I would hazard to guess that Syd may have rolled back recent changes in the DB. That may mean that someone either has to reupload the factorization of the c116 or, assuming it may have been deleted, do it again.....

[Edited to add: Ooops. Looks like a duplicate entry. Check out [URL="http://factordb.com/index.php?id=1100000000508756358"]this[/URL] and [URL="http://factordb.com/index.php?id=1100000000508647107"]this[/URL]. Wonder how that will affect things......]

My script is still running and I've uploaded the ending up to +1387, there's a c116 there too (NFS is running).

So we have to fill in from [URL="http://factordb.com/sequences.php?se=1&eff=2&aq=4788&action=last20&fr=0&to=100"]here[/URL] to [URL="http://factordb.com/sequences.php?se=1&aq=40957875574394316311003047843043516950271720473684192538168111457395057835508589937432267551919865595270070289148056&action=last20&fr=0&to=100"]here[/URL].
It was not only Dubslow, maybe Alex, Jayson?

We need everyone who ran that 2^4, 2^3*5, 2^3 stretch. (Or of course it can be retraced in about one day.)

I haven't found many factors over the last few days, and haven't kept any of them as they usually were relatively small ECM factors. I remember one p51, but I haven't kept that one, either, since someone else had already submitted it.

Edit: I had an old .elf file, but it had data only up to i2998. That part agrees with an .elf file I just downloaded. I had two pages with factorizations left in my brower cache, but the factors appear in 4788.elf or 409578...8056.elf so they are not from the missing part.

Just in case:
The log file of my script, which runs ECM on the last composites of 4788.
Factors of terms 3373-3408, so only 3372 is missing.
[CODE]23:35:35 4788.3373:C113 B1=1000000 35325380801491504748070045973 added: 1
23:36:17 4788.3374:C81 B1=1000000 2141317713659627997057622792876571997551327467 added: 1
23:37:26 4788.3376:C85 B1=1000000 7699913161822247573 added: 2
23:37:28 4788.3377:C100 B1=1000000 17585202048994367 added: 0
23:37:35 4788.3378:C112 B1=1000000 9613645891265309 added: 0
23:37:42 4788.3380:C113 B1=1000000 578670248512500961 added: 0
23:38:16 4788.3381:C100 B1=1000000 1101870405375551814556296007009 added: 1
23:38:23 4788.3382:C106 B1=1000000 1108503548981 added: 1
23:38:30 4788.3382:C71 B1=1000000 6806477373344263446350885761 added: 0
23:38:46 4788.3383:C81 B1=1000000 169348724568606483653914130855262698915900685289927 added: 0
23:40:28 4788.3386:C105 B1=1000000 60624096937583 added: 0
01:32:21 4788.3387:C114 B1=44000000 112154658209074691222546265849621937434966836228837 added: 1
01:34:58 4788.3388:C111 B1=4000000 33866066054022123488931023659 added: 2
01:35:17 4788.3390:C95 B1=4000000 646482538389617412489407 added: 1
01:35:26 4788.3391:C115 B1=4000000 99721907 added: 0
01:35:38 4788.3392:C111 B1=4000000 227006464964297 added: 0
01:35:55 4788.3393:C77 B1=4000000 3092613893973696942891592909155617 added: 1
01:36:42 4788.3394:C90 B1=4000000 79212242071005124902911402723062272765456061223977 added: 1
01:46:04 4788.3397:C113 B1=4000000 1958807247942367721 added: 0
01:46:22 4788.3399:C93 B1=4000000 218182820706493 added: 0
01:47:18 4788.3402:C85 B1=4000000 1968963883404327666207731371 added: 1
01:47:28 4788.3403:C106 B1=4000000 88211778830249 added: 0
01:47:45 4788.3404:C104 B1=4000000 4833935116244443039 added: 0
01:48:03 4788.3405:C104 B1=4000000 1349145807142186249406051574127990099 added: 1
01:48:19 4788.3408:C107 B1=4000000 4492625450259614471 added: 0
01:48:37 4788.3408:C88 B1=4000000 5807928179646144670796389 added: 0[/CODE]Line 3387 was a nice shot.

A lurker

I am bowing out at +1398, c112. Put one line in your elf file and you can go with aliqueit -e
[CODE] 1397 . 1001777285392569572904290646390787226308237439383461254469983491988408403137367200479555518410377674168016748413824068285936 = 2^4 * 31 * 1447 * 18103888892349677 * 1922571138731027507 * 334759903278150757688691430026991 * 119793497488326129606597958143119427551092583328047
[/CODE]

I'll run the c108 for closure.

doing i3372