![]() |
[B]QUEUED AS C168_434040_3104[/B]
[QUOTE=richs;543943]C168 from aliquot 434040, i3104, tested to t51, for 14e: [CODE]# norm 2.582511e-016 alpha -8.066147 e 4.421e-013 rroots 3 n: 787138472477216198384556294823118346717661942769195559625443853931194189459063751394270544046390314892170233126467399893934430448008090894783277988649941877409628077709 skew: 97595741.37 c0: 8022476780927537013878704153755523583168313 c1: -844520378148615856269491730954439965 c2: 15192071173796182389539327165 c3: 373160219084471613535 c4: -402863664628 c5: 1320 Y0: -901769291156177765304112392468580 Y1: 2439108564156793 rlim: 55000000 alim: 55000000 lpbr: 31 lpba: 31 mfbr: 62 mfba: 62 rlambda: 2.6 alambda: 2.6 [/CODE] 300 cpu thread-hours for poly. Suggest 20-200M range for sieving. I will handle LA.[/QUOTE] Based on swellman's advice, I have modified the rlim/alim parameters and slightly increased the Q range to obtain a greater number of relations. [CODE]n: 787138472477216198384556294823118346717661942769195559625443853931194189459063751394270544046390314892170233126467399893934430448008090894783277988649941877409628077709 skew: 97595741.37 c0: 8022476780927537013878704153755523583168313 c1: -844520378148615856269491730954439965 c2: 15192071173796182389539327165 c3: 373160219084471613535 c4: -402863664628 c5: 1320 Y0: -901769291156177765304112392468580 Y1: 2439108564156793 rlim: 134000000 alim: 134000000 lpbr: 31 lpba: 31 mfbr: 62 mfba: 62 rlambda: 2.6 alambda: 2.6 type: GNFS[/CODE] Suggested range 10-200M. |
15e Candidate
[B]QUEUED AS 83_139m1[/B]
C263 from the MWRB file with OPN weight 24951. Ready for 15e queue. [CODE]n: 12364762892471073506519769982508250686607918983881339929208149351946116324078345259589751990410443726654465899975381288381005312944361250326124328083721805393249245957713033033181923503559274308305578867857669895754595597577196658127229875701842056636978880532929 # 83^139-1, difficulty: 266.75, skewness: 0.48, alpha: 0.00 # cost: 2.9112e+19, est. time: 13862.86 GHz days (not accurate yet!) skew: 0.479 c6: 83 c0: -1 Y1: -1 Y0: 137656310293626928473255626953462008797108987 type: snfs rlim: 268000000 alim: 268000000 lpbr: 32 lpba: 32 mfbr: 64 mfba: 64 rlambda: 2.7 alambda: 2.7[/CODE] Trial sieving 5K blocks. [CODE] Q Yield 20M 10610 60M 9985 100M 9598 200M 8286 280M 7471[/CODE] |
[QUOTE=pinhodecarlos;543809]Can I have an update from you all in terms of work available to be added to the grid, 14e and 15e queue? It’s that time of the year again for the Pentathlon ( start 5th May 2020) this year the five projects are chosen by a small group of the organisers which means NFS@Home can be chosen again.
The BOINC Pentathlon consists of 5 disciplines: Marathon (14 days) Sprint (3 days) City Run (5 days) Cross Country (5 days) Javelin Throw (5 x 1 day, only each team's third best daily score counts)[/QUOTE] Carlos - Where are we with regards to the Pentathlon? If NFS@Home is selected, we likely need more work in the 14e queue. |
Sean, from what I can see from the server it looks fine, only more work for the 16e queue but Greg will pick up on this. As you might not be aware I’m not part of this challenge organisation therefore I can only give you a heads up to have the server full, just for the case, I don’t know if it will be chosen, only Greg knows. You can discuss this with Greg in private but please let me out of the discussion since I’ll be participating in the challenge, I don’t want to have privileged information.
Tip: take a screenshot today of the server queue regarding “in progress”, if you see this increasing dramatically it means the project has been chosen and clients are bunkering. |
Well I won’t ask Greg to break a confidence, I’ll just watch for a sudden drain on the queues. It’s pretty apparent when it happens. I’m not worried about 15e but we may need more for 14e, play it by ear.
|
[QUOTE=swellman;544226]Well I won’t ask Greg to break a confidence, I’ll just watch for a sudden drain on the queues. It’s pretty apparent when it happens. I’m not worried about 15e but we may need more for 14e, play it by ear.[/QUOTE]
Don’t forget highest credit comes from the 16e queue. |
If you need some more work the next lot from the Brent tables would be:
(18^197-1)/189727955598289393777399 (19^193+1)/271702852012782057599427602380 (24^179-1)/3054213109481693 (30^167-1)/29 (43^151+1)/58788017642734307974701740364532 (62^137-1)/24713408295938873981 (75^131-1)/59563948827208938194 (83^128+1)/911324598748213967918713898735928304642 (86^127+1)/39291979136297696304985687521312606824391 I'll test sieve a few and post results, working from the bottom of this list upwards. If we don't get selected for the challenge I should be able to do LA for the Brent tables entries as fast as they get sieved. But I won't be sorry if they get sieved much faster than that! Chris |
Chris -
Can you generate the polynomials and test sieve for the last two Brent numbers in this post [url]https://www.mersenneforum.org/showpost.php?p=543870&postcount=2351?[/url] I have not had time to finish the list. The first six (from the top) are queued. Thank you for posting this work. Even if NFS@Home is not selected for the Pentathlon, we always seem to struggle to feed 14e! Eta these are the two composites needing polys/test sieving: [code] (86^127-1)/188429252758467634112856126883772417755036448095225565 (93^124+1)/2309044301090448461075440205529394[/code] Thank you! |
[B]QUEUED AS 515__401_5m1[/B]
C152 from the OPN t800 file. 515380651092796114239414194849764516701117416486401^5-1 p51^5-1 [ a.k.a. Phi_5(Phi_5(Phi_7(162709)/7/71/p13)/11/22031/14061661)/5/11/811/38461/233201/17187451/p30 ] [CODE]n: 44071437583252912142752462367945315674018279237169592050591371271797186730788474460401519679093653784912147928829693795988493030787567502948738092609571 lss: 0 Y0: -190522528041166981207991212494 Y1: 1548557929493761 c0: 127839116660170048027415124998868953885 c1: 204738353026674032839864497113727 c2: 18289350142202398864067351 c3: -13381769200588442295 c4: -1623493610308 c5: 175560 skew: 5400478.34 type: gnfs rlim: 33500000 alim: 33500000 lpbr: 29 lpba: 29 mfbr: 57 mfba: 57 rlambda: 2.5 alambda: 2.5[/CODE] Trial sieving 5K blocks. [CODE] Q Yield [B]10M[/B] 11113 20M 12060 40M 9411[/CODE] |
[B]QUEUED AS f86_127p1[/B]
[code] # (86^127+1)/39291979136297696304985687521312606824391 # Built Thu Apr 30 19:51:25 2020 # Estimated SNFS difficulty is 246, GNFS equivalent is 177, GNFS difficulty is 206, degree 6 # Base1 86: 2 43 # Base2 1: n: 12217979810913129107446613665785386400072524716505529029273729809930116874341926089641673651433666126348509357752835013440139599456663698714649918334103665946056474170323555809437932963339646714293702027767 type: snfs # c6 86: 2 43 c6: 86 # c0 1: c0: 1 # Y0 = 86^21 Y0: 42117974383768340415833307871690448961536 # Y1 = 1^0 Y1: 1 # msieve rating: skew 0.48, size 2.852e-12, alpha 1.727, combined = 2.583e-13 rroots = 0 skew: 0.476 rlim: 134000000 alim: 134000000 lpbr: 31 lpba: 31 mfbr: 62 mfba: 91 rlambda: 2.6 alambda: 3.5 [/code] But the yield varies eratically. I got this trial sieving 1k ranges: [code] Yield range special-Q 3152 20M 78 947 80M 34 1614 134M 64 1284 160M 54 969 220M 46 [/code] The last column is how many special-Q lasieve4I14e said it found in each range. So I retested it with 10k ranges overnight: [code] 24063 20M 616 13928 80M 490 10896 134M 450 13803 160M 606 11144 220M 542 [/code] Based on those yields I estimate sieving from 20M to 170M should get enough relations. Adjusting for the number of special-Q in each range I test sieved should be more accurate. But what should I assume for the average number of special-Q in a range of say 10M? Chris |
[QUOTE=swellman;544310]Chris -
Can you generate the polynomials and test sieve for the last two Brent numbers in this post [url]https://www.mersenneforum.org/showpost.php?p=543870&postcount=2351?[/url] I have not had time to finish the list. The first six (from the top) are queued. Thank you for posting this work. Even if NFS@Home is not selected for the Pentathlon, we always seem to struggle to feed 14e! Eta these are the two composites needing polys/test sieving: [code] (86^127-1)/188429252758467634112856126883772417755036448095225565 (93^124+1)/2309044301090448461075440205529394[/code] Thank you![/QUOTE] OK, I'll do them next, when I have some free time. And then the rest of the next lot I posted. Chris |
| All times are UTC. The time now is 10:17. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.