Status of p-1.... - Page 4

garo · 2005-06-29, 13:30

ou are right. It would be much simpler and less time-consuming to fetch those numbers from the server. Still, I would encourage some of Marin's Mersennaries to put some effort into this - particularly those people who use artificially large B1,B2 for doublechecks such as James Heinrich (sp?). It would be nice if those people could do some P-1 for untested numbers especially since they are willing to spend more time per number to get more factors!

dave_0273 · 2005-07-03, 05:49

Status of p-1 using the 1st July, 2005 status files

Code:

          M         NUMBER
         0-15          0
          16           0
          17           0
          18           0
          19         431
          20        1100
          21         530
          22         315
          23         303
          24         281
          25         162
          26         152
          27         107
          28          36
          29          33
          30           0

Code:

0.1MRANGE    NUMBER    CHANGE
   19.0         0         0
   19.1         0         0
   19.2         1         0
   19.3         0         0
   19.4         0         0
   19.5         0         0
   19.6         0        -1
   19.7       124      -109
   19.8       126        -5
   19.9       180        -1
   20.0       128        -5
   20.1        90         0
   20.2       117         0
   20.3       101         0
   20.4       108         0
   20.5       125         0
   20.6       112         0
   20.7        92         0
   20.8       126         0
   20.9       101         0

We are coming along quite nicely. Everything up to (and including) 19.6 is now complete. The exponent in the 19.2-19.3M range showed above is currently assigned to somone on primenet, therefore mersenne-aries won't touch it.

cheesehead · 2005-07-13, 07:02

Quote:

Originally Posted by dave_0273

The other thing that we would need is for another group to be working with us doing the trail factoring before we do the p-1.

Or ... Mersenne-aries could both TF and P-1 each number. Just check out some for TF, but don't report TF results until after doing P-1, then report both.

Or check out TF assignments, but do only P-1 using the LMHed TF limits, report the P-1, then unreserve the TF assignments. But there's a fatal flaw in this method -- see below.

Quote:

Originally Posted by dave_0273

However, one the biggest reasons why I have never bothered to go ahead of the leading edge of LL testing is because if people really wanted to do that sort of work, they could always do it the semi-automated way. They could reserve 50 or so exponents, do the p-1 and then release them again. Because the work is therefore technically assigned through primenet, they wouldn't be duplicating work and they wouldn't be stepping on each others toes.

This doesn't work with mersenne-aries because you just can't get enough work this way. The majority of exponents are p-1ed on the first LL test. Even when I tried to reserve 50 exponents, I would find that I would get less than 5 that would require a p-1 test.

But if Mersenne-aries used TF reservations instead of LL reservations, and both TFed and P-1ed, the latter objection disappears, doesn't it?

Of course, if Mersenne-aries did only P-1, but not actual TF, on TF assignments, then after unreserving those TF assignments the next Mersenne-ary to get the same TF reservation would waste a bunch of P-1 unless s/he checked the P-1 status first ... but that's difficult if pminus1.txt hasn't yet been updated, so maybe this idea of TF-less TFs won't work.

dave_0273 · 2005-07-14, 03:15

Quote:

Of course, if Mersenne-aries did only P-1, but not actual TF, on TF assignments, then after unreserving those TF assignments the next Mersenne-ary to get the same TF reservation would waste a bunch of P-1 unless s/he checked the P-1 status first ... but that's difficult if pminus1.txt hasn't yet been updated, so maybe this idea of TF-less TFs won't work.

Very true. That is why I think that it would be better for people to reserve first time LL tests instead of trial factoring. Also, this way they have already been trail factored up to its default limit. I think that this would be preferable, rather than p-1ing an exponent and then doing the remaining trial factoring.

When I said that it wouldn't work with mersenne-aries, what I meant was that reserving exponents through primenet wouldn't work if you wanted to go ahead of the leading edge of double-checking. It would work fine however if you wanted to go ahead (or work co-currently) with the leading edge of first time LLing.

garo · 2005-07-14, 08:04

Yes dave, you are absolutely right. I agree. But we could have people with "excess" P-1 power to try that on a few numbers. And you don't even have to change the worktodo. Just insert SequentialWork=1 in prime.ini and all the P-1s will be finished before the first LL test is started. So by having a number that you are already LL testing at the top of the work queue you will never have to do any LL testing on the numbers you want to do a P-1 on.

markr · 2005-07-14, 23:23

[pedant]
SequentialWork=0
will stop it from doing the lines in order.
[/pedant]

garo · 2005-07-15, 06:07

Riiiiiight!

dave_0273 · 2005-07-18, 14:58

Status of p-1 using the 18th July status files

Code:

          M        CHANGE 
         0-15          0
          16           0
          17           0
          18           1
          19         224
          20        1053
          21         529
          22         314
          23         303
          24         283
          25         164
          26         154
          27         112
          28          40
          29          45
          30           0

Code:

0.1MRANGE    NUMBER    CHANGE
   19.0         0         0
   19.1         0         0
   19.2         1         0
   19.3         0         0
   19.4         0         0
   19.5         0         0
   19.6         0         0
   19.7       124         0
   19.8         1      -125
   19.9        98       -82
   20.0        83       -45
   20.1        90         0
   20.2       115        -2
   20.3       101         0
   20.4       108         0
   20.5       125         0
   20.6       112         0
   20.7        92         0
   20.8       126         0
   20.9       101         0

James Heinrich · 2005-08-06, 13:03

Status of P-1 using the 1 Aug 2005 status files:

Code:

 M         NUMBER
 18           1
 19           0
 20         962
 21         521
 22         313
 23         299
 24         281
 25         166
 26         152
 27         116
 28          49
 29          53
 30           0
 31           0
 32           0
 33         335
 34         261
 35          82
 36           1
 37          24

Code:

  0.1M RANGE   NUMBER    CHANGE
   18.6         1         0
   18.7         0         0
   18.8         0         0
   18.9         0         0
   19.0         0         0
   19.1         0         0
   19.2         0        -1
   19.3         0         0
   19.4         0         0
   19.5         0         0
   19.6         0         0
   19.7         0      -124
   19.8         0        -1
   19.9         0       -98
   20.0        34       -49
   20.1        90         0
   20.2        73       -42
   20.3       101         0
   20.4       108         0
   20.5       125         0
   20.6       112         0
   20.7        92         0
   20.8       126         0
   20.9       101         0
   21.0        98         0
   21.1        84         0
   21.2        94         0
   21.3        49         0
   21.4        24         0
   21.5        32         0
   21.6        33         0
   21.7        32         0
   21.8        32         0
   21.9        43         0
   22.0        40         0
   22.1        28         0
   22.2        25         0
   22.3        28         0
   22.4        33         0
   22.5        37         0
   22.6        38         0
   22.7        36         0
   22.8        21         0
   22.9        27         0
   23.0        33         0
   23.1        27         0
   23.2        30         0
   23.3        33         0
   23.4        29         0
   23.5        24         0

James Heinrich · 2005-08-17, 12:36

Status of P-1 using the 17 Aug 2005 status files:

Code:

 M         NUMBER
 20         943
 21         520
 22         313
 23         300
 24         285
 25         168
 26         153
 27         123
 28          55
 29          66
 30           0
 31           0
 32           0
 33         334
 34         263
 35          91
 36           1
 37          24
 38           1

Code:

  0.1M RANGE   NUMBER    CHANGE
   20.0        34         0
   20.1        90         0
   20.2        54       -19
   20.3       101         0
   20.4       108         0
   20.5       125         0
   20.6       112         0
   20.7        92         0
   20.8       126         0
   20.9       101         0
   21.0        97        -1
   21.1        84         0
   21.2        94         0
   21.3        49         0
   21.4        24         0
   21.5        32         0
   21.6        33         0
   21.7        32         0
   21.8        32         0
   21.9        43         0
   22.0        40         0
   22.1        28         0
   22.2        25         0
   22.3        28         0
   22.4        33         0
   22.5        37         0
   22.6        38         0
   22.7        36         0
   22.8        21         0
   22.9        27         0
   23.0        33         0
   23.1        27         0
   23.2        30         0
   23.3        33         0
   23.4        29         0
   23.5        24         0
   23.6        35         0
   23.7        28         0
   23.8        25         0
   23.9        36         0
   24.0        39         0
   24.1        25         0
   24.2        33         0
   24.3        28         0
   24.4        31         0
   24.5        35         0
   24.6        30         0
   24.7        22         0
   24.8        28         0
   24.9        14         0

James Heinrich · 2005-10-02, 23:31

Status of P-1 using the 22 September 2005 status files:

Code:

 M         NUMBER
 20         734
 21         522
 22         316
 23         300
 24         291
 25         179
 26         167
 27         145
 28          67
 29          94
 30           5
 31           0
 32           0
 33         333
 34         287
 35         103
 36           1
 37          25
 38           3
 39           0
 40           0
 41           1

Code:

  0.1M RANGE   NUMBER    CHANGE
   20.0        33        -1
   20.1        44       -46
   20.2         0       -54
   20.3       101         0
   20.4         0      -108
   20.5       125         0
   20.6       112         0
   20.7        92         0
   20.8       126         0
   20.9       101         0
   21.0        97         0
   21.1        84         0
   21.2        93        -1
   21.3        49         0
   21.4        24         0
   21.5        32         0
   21.6        33         0
   21.7        33         1
   21.8        33         1
   21.9        44         1
   22.0        40         0
   22.1        28         0
   22.2        25         0
   22.3        28         0
   22.4        33         0
   22.5        37         0
   22.6        38         0
   22.7        37         1
   22.8        23         2
   22.9        27         0
   23.0        33         0
   23.1        27         0
   23.2        30         0
   23.3        33         0
   23.4        29         0
   23.5        24         0
   23.6        35         0
   23.7        28         0
   23.8        25         0
   23.9        36         0
   24.0        39         0
   24.1        26         1
   24.2        33         0
   24.3        30         2
   24.4        31         0
   24.5        36         1
   24.6        31         1
   24.7        23         1
   24.8        28         0
   24.9        14         0

2005-07-03, 05:49	#35
dave_0273 Oct 2003 Australia, Brisbane 2×5×47 Posts	Status of p-1 using the 1st July, 2005 status files Code: M NUMBER 0-15 0 16 0 17 0 18 0 19 431 20 1100 21 530 22 315 23 303 24 281 25 162 26 152 27 107 28 36 29 33 30 0 Code: 0.1MRANGE NUMBER CHANGE 19.0 0 0 19.1 0 0 19.2 1 0 19.3 0 0 19.4 0 0 19.5 0 0 19.6 0 -1 19.7 124 -109 19.8 126 -5 19.9 180 -1 20.0 128 -5 20.1 90 0 20.2 117 0 20.3 101 0 20.4 108 0 20.5 125 0 20.6 112 0 20.7 92 0 20.8 126 0 20.9 101 0 We are coming along quite nicely. Everything up to (and including) 19.6 is now complete. The exponent in the 19.2-19.3M range showed above is currently assigned to somone on primenet, therefore mersenne-aries won't touch it.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Status	Primeinator	Operation Billion Digits	5	2011-12-06 02:35
62 bit status	1997rj7	Lone Mersenne Hunters	27	2008-09-29 13:52
OBD Status	Uncwilly	Operation Billion Digits	22	2005-10-25 14:05
1-2M LLR status	paulunderwood	3*2^n-1 Search	2	2005-03-13 17:03
Status of 26.0M - 26.5M	1997rj7	Lone Mersenne Hunters	25	2004-06-18 16:46

2005-06-29, 13:30	#34
garo Aug 2002 Termonfeckin, IE 5320₈ Posts	ou are right. It would be much simpler and less time-consuming to fetch those numbers from the server. Still, I would encourage some of Marin's Mersennaries to put some effort into this - particularly those people who use artificially large B1,B2 for doublechecks such as James Heinrich (sp?). It would be nice if those people could do some P-1 for untested numbers especially since they are willing to spend more time per number to get more factors!

2005-07-14, 08:04	#38
garo Aug 2002 Termonfeckin, IE AD0₁₆ Posts	Yes dave, you are absolutely right. I agree. But we could have people with "excess" P-1 power to try that on a few numbers. And you don't even have to change the worktodo. Just insert SequentialWork=1 in prime.ini and all the P-1s will be finished before the first LL test is started. So by having a number that you are already LL testing at the top of the work queue you will never have to do any LL testing on the numbers you want to do a P-1 on.

2005-07-14, 23:23	#39
markr "Mark" Feb 2003 Sydney 3×191 Posts	[pedant] SequentialWork=0 will stop it from doing the lines in order. [/pedant]

2005-07-15, 06:07	#40
garo Aug 2002 Termonfeckin, IE 2⁴×173 Posts	Riiiiiight!