No update for ages.

Greg, how many curves have you run? I don't want to start the team sieve until at least half of t55 has been done. Preferably a full t55.

[QUOTE=10metreh;226999]No update for ages.

Greg, how many curves have you run? I don't want to start the team sieve until at least half of t55 has been done. Preferably a full t55.[/QUOTE]

Hmmm... According to my estimate, full t55 is needed for a c170. (please correct me, if I'm wrong.)

Edit: I just see that I have not yet reportet the [B]82 curves @26e7[/B] which I have done back on Aug. 5th.

I will run a few more curves.

Alternate sieving parameters for c170 poly
 

These parameters differ from the ones above in that it allows up to three large primes on the algebraic side.

[code]n: 31312681856591762976684825948611411853648506930718408786922952694966820760977803934965693400499529851375037912983239126649207012737394067178518887401399185420987310860499
# norm 1.089488e-16 alpha -8.144343 e 2.852e-13 rroots 5
skew: 2848875.02
c0: 3449752476991340409710593294897864121568
c1: 3679068299798050640485923392826756
c2: -55695962181000919237307903624
c3: 5626603601260154351771
c4: 6624408564633178
c5: 64149120
Y0: -217612366832903667482868415880575
Y1: 542063406908335635313
rlim: 33554431
alim: 33554431
lpbr: 30
lpba: 30
mfbr: 60
mfba: 87
rlambda: 2.6
alambda: 3.6[/code]

With this, the sieving range is from Q=20M to about 90M on the algebraic side with 15e. Even with a smaller fb limit, the yield is still greater, meaning fewer Q is needed. The time to sieve each Q is increased (more time spent in mpqs) but the total estimated sieve time is slightly reduced.

[QUOTE=10metreh;226999]Greg, how many curves have you run? I don't want to start the team sieve until at least half of t55 has been done. Preferably a full t55.[/QUOTE]
All my curves are in the database. 1863 @ B1=26e7 = 0.24*t55

360@26e7, no factor

48 @ B1=26e7, B2=2716922571100, no factor.

ECM anyone?? Now, as the sieving for 2801^79-1 is done, there should be some free resources out there?

[strike]105 @ B1=26e7, B2=3178559884516, no factor[/strike]

edit: oops, forgot to edit the input file name in my batchfile, these 105 curves have been run on another number.

What's the current curve count for the c170?

I am feebly doing some B1=11e7 curves, but will not get very far (can manage a bit more than 100 per day).

[QUOTE=jrk;228492]What's the current curve count for the c170?

I am feebly doing some B1=11e7 curves, but will not get very far (can manage a bit more than 100 per day).[/QUOTE]

I think 105 less than reported in the old DB - as stated in my posting above, I have accidentally run 105 curves on the wrong number and only recognized this [I]after[/I] reporting the curves.

[QUOTE=jrk;228492]What's the current curve count for the c170?[/QUOTE]You can see the current work, as reported, on the composite page in the *old* DB. Check [URL="http://factordb.com/search.php?id=167332106&adv167332106=%3E+%3E"]here[/URL]. ([strike]Only valid, I think, if you've got credentials for the old DB...[/strike]) Let me know if nothing shows, we can paste the current page here....

[Edit: Never mind, it does show if you're signed out....guess I misremembered.]

[QUOTE=Andi47;228493]I think 105 less than reported in the old DB - as stated in my posting above, I have accidentally run 105 curves on the wrong number and only recognized this [I]after[/I] reporting the curves.[/QUOTE]

I re-did the curves (this time correctly), so the number of my reported curves now corresponds to the number of curves which I have done.