mersenneforum.org

mersenneforum.org (https://www.mersenneforum.org/index.php)
-   Miscellaneous Math (https://www.mersenneforum.org/forumdisplay.php?f=56)
-   -   bbb120 (https://www.mersenneforum.org/showthread.php?t=24112)

bbb120 2019-02-26 02:24

bbb120
 
I register this forum about ten years ago ,
my username is bbb120(from China),but it is
impossible for me to get my password by email ,
because the bbb120 is not in use,
I do not know why !
I register this old name by an new email today ,
but how can I find my old posts(maybe thread),
my English is not very well,there maybe some
mistake in this thread.

bbb120 2019-02-26 04:38

I make a mistake ,
my old username is "aaa120" not "bbb120"
but I forgot the password of aaa120,and I can not
get the password of aaa120

bbb120 2019-02-26 04:44

[QUOTE=yoyo;471283]A yoyo@home user found a P73 for R1186 (10^593+1):

[CODE]
GMP-ECM 7.0.5-dev [configured with GMP 6.1.2, --enable-asm-redc] [ECM]
Input number is 9090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909091 (592 digits)
[Tue Nov 07 18:14:21 2017]
Using MODMULN [mulredc:4, sqrredc:4]
Using B1=110000000, B2=829850101096, polynomial Dickson(30), sigma=0:16299314430696221325
dF=120960, k=5, d=1291290, d2=17, i0=69
Expected number of curves to find a factor of n digits:
35 40 45 50 55 60 65 70 75 80
34 134 608 3119 17689 110056 743875 5417128 4.2e+07 3.6e+08
Writing checkpoint to checkpnt at p = 20333393
Writing checkpoint to checkpnt at p = 40506859
Writing checkpoint to checkpnt at p = 60560629
Writing checkpoint to checkpnt at p = 80690453
Writing checkpoint to checkpnt at p = 101083799
Writing checkpoint to checkpnt at p = 110000000
Step 1 took 3247765ms
Estimated memory usage: 1.64GB
Initializing tables of differences for F took 1984ms
Computing roots of F took 63375ms
Building F from its roots took 27093ms
Computing 1/F took 12141ms
Initializing table of differences for G took 2609ms
Computing roots of G took 51422ms
Building G from its roots took 26860ms
Computing roots of G took 55781ms
Building G from its roots took 27016ms
Computing G * H took 6610ms
Reducing G * H mod F took 9781ms
Computing roots of G took 56922ms
Building G from its roots took 26859ms
Computing G * H took 6766ms
Reducing G * H mod F took 9797ms
Computing roots of G took 57312ms
Building G from its roots took 26594ms
Computing G * H took 6750ms
Reducing G * H mod F took 9829ms
Computing roots of G took 57171ms
Building G from its roots took 27079ms
Computing G * H took 6422ms
Reducing G * H mod F took 9390ms
Computing polyeval(F,G) took 57781ms
Computing product of all F(g_i) took 344ms
Step 2 took 644328ms
********** Factor found in step 2: 2909076542620598524499532435958736860811671130747534094532375046661903161
Found prime factor of 73 digits: 2909076542620598524499532435958736860811671130747534094532375046661903161
Probable prime cofactor 3125015432807993452395038634013309617867717582914358894173268713097150537376427232621985983364362381037572308793912508473244215581788783050366433021306602205095695585123360825687037384480936324147844060907653636389193668837605678869741546508709934354266735495475343271268446929051785779649633066534259397463567093895758026730277823815590724554798361272711560580416081789809541777798773606334712701416644206700894936206530047039287732255861170965984971136826555598096883703505206688714709410112221639166983114001153395131 has 520 digits
Report your potential champion to Richard Brent <champs@rpbrent.com>
(see http://wwwmaths.anu.edu.au/~brent/ftp/champs.txt)
Peak memory usage: 1469MB
[/CODE][/QUOTE]

Great!
Good Job!

bbb120 2019-02-26 04:44

[QUOTE=yoyo;471283]A yoyo@home user found a P73 for R1186 (10^593+1):

[CODE]
GMP-ECM 7.0.5-dev [configured with GMP 6.1.2, --enable-asm-redc] [ECM]
Input number is 9090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909090909091 (592 digits)
[Tue Nov 07 18:14:21 2017]
Using MODMULN [mulredc:4, sqrredc:4]
Using B1=110000000, B2=829850101096, polynomial Dickson(30), sigma=0:16299314430696221325
dF=120960, k=5, d=1291290, d2=17, i0=69
Expected number of curves to find a factor of n digits:
35 40 45 50 55 60 65 70 75 80
34 134 608 3119 17689 110056 743875 5417128 4.2e+07 3.6e+08
Writing checkpoint to checkpnt at p = 20333393
Writing checkpoint to checkpnt at p = 40506859
Writing checkpoint to checkpnt at p = 60560629
Writing checkpoint to checkpnt at p = 80690453
Writing checkpoint to checkpnt at p = 101083799
Writing checkpoint to checkpnt at p = 110000000
Step 1 took 3247765ms
Estimated memory usage: 1.64GB
Initializing tables of differences for F took 1984ms
Computing roots of F took 63375ms
Building F from its roots took 27093ms
Computing 1/F took 12141ms
Initializing table of differences for G took 2609ms
Computing roots of G took 51422ms
Building G from its roots took 26860ms
Computing roots of G took 55781ms
Building G from its roots took 27016ms
Computing G * H took 6610ms
Reducing G * H mod F took 9781ms
Computing roots of G took 56922ms
Building G from its roots took 26859ms
Computing G * H took 6766ms
Reducing G * H mod F took 9797ms
Computing roots of G took 57312ms
Building G from its roots took 26594ms
Computing G * H took 6750ms
Reducing G * H mod F took 9829ms
Computing roots of G took 57171ms
Building G from its roots took 27079ms
Computing G * H took 6422ms
Reducing G * H mod F took 9390ms
Computing polyeval(F,G) took 57781ms
Computing product of all F(g_i) took 344ms
Step 2 took 644328ms
********** Factor found in step 2: 2909076542620598524499532435958736860811671130747534094532375046661903161
Found prime factor of 73 digits: 2909076542620598524499532435958736860811671130747534094532375046661903161
Probable prime cofactor 3125015432807993452395038634013309617867717582914358894173268713097150537376427232621985983364362381037572308793912508473244215581788783050366433021306602205095695585123360825687037384480936324147844060907653636389193668837605678869741546508709934354266735495475343271268446929051785779649633066534259397463567093895758026730277823815590724554798361272711560580416081789809541777798773606334712701416644206700894936206530047039287732255861170965984971136826555598096883703505206688714709410112221639166983114001153395131 has 520 digits
Report your potential champion to Richard Brent <champs@rpbrent.com>
(see http://wwwmaths.anu.edu.au/~brent/ftp/champs.txt)
Peak memory usage: 1469MB
[/CODE][/QUOTE]

Great!
Good Job!

Batalov 2019-02-26 07:43

[QUOTE=bbb120;509450]...but how can I find my old posts(maybe thread),
[/QUOTE]
[URL]https://mersenneforum.org/search.php?searchid=2471168[/URL]
[URL]https://mersenneforum.org/search.php[/URL] :: Search by user name


What were you trying to find there?

Batalov 2019-02-26 07:49

One thing that we will try to discourage you to do is:
find some 8-year old post then quote it completely and simply add: 'that's great!'

You've already done it twice and it is annoying. This behavior is called 'necroposting'.
Don't do that.

bbb120 2019-02-28 07:05

[QUOTE=Puzzle-Peter;373565]Just for fun I tried 2^73360+10711 once again with PRIMO 4.10. This version was successful in test1 thanks to the new discriminant tables. It will be an on-and-off job, but I will continue this run unless somebody else would rather do it.[/QUOTE]

You can use mathematica ,function PrimeQ[2^73360+10711]

[CODE]MillerRabin[n0_,a0_]:=Module[{n=n0,a=a0,s,m,t1,k},
s=0;m=n-1;While[Mod[m,2]==0,m=m/2;s=s+1];
t1=PowerMod[a,m,n];
If[t1==1,Return[True]];
k=0;While[k<s-1&&t1!=n-1,k=k+1;t1=Mod[t1^2,n]];
If[t1==n-1,Return[True],Return[False]]
]
[/CODE]
Miller Rabin code by using mathematica,

MillerRabin[2^73360+10711, #] & /@ {17, 257, 65537, 10^200 + 267}
{True, True, True, True}
this is too fast,ECPP is too slow,

miller rabin is simple and realible!

bbb120 2019-02-28 07:21

[QUOTE=philmoore;157427]Congratulations to Ben Maloney (paleseptember) who discovered the probable prime [TEX]2^{1518191}+75353[/TEX]. At 457,022 decimal digits, it should soon appear as the new probable prime record at the website of Henri and Renaud Lifchitz, [/QUOTE]

2887148238050771212671429597130393991977609459279722700926516024197432\
3037991527331163289831446392259419778031109293496555784189494417409338\
0561511397999942154241693397290542371100275104208013496673175515285922\
6962916775325475044445856101949404200039904432116776619949629539250452\
6987193290703735640322737012784538991261203092448414947289768854060249\
76768122077071687938121709811322297802059565867
this 397 digits composite number pass the miller rabin test base from 2 to 306,
so you should use at least one lucas test on probable prime !

Batalov 2019-02-28 15:20

You have been previously warned.
For now, your non-sequitur necroposts will be moved here.
Later you may receive a ban.


[COLOR=DarkRed]If you want to say something new about a discussion that ended several years ago - start a new thread![/COLOR]

retina 2019-02-28 16:52

[QUOTE=Batalov;509679][COLOR=DarkRed]If you want to say something new about a discussion that ended several years ago - start a new thread![/COLOR][/QUOTE]Why is it necessary to start a new topic? I haven't seen anything on this board that disallows responding to an existing topic with pertinent information.

Uncwilly 2019-02-28 19:08

[QUOTE=retina;509685]Why is it necessary to start a new topic? I haven't seen anything on this board that disallows responding to an existing topic with pertinent information.[/QUOTE]Necroposting a few time is in the spammer's MO. It is also easier to find things to tack onto an old post to appear to be adding valid comments.

Batalov 2019-02-28 21:26

[QUOTE=retina;509685]Why is it necessary to start a new topic? I haven't seen anything on this board that disallows responding to an existing topic with pertinent information.[/QUOTE]
Glad you asked!

Most forums do (or recommend) this by default:
[QUOTE="https://communitybuilding.stackexchange.com/questions/2632/why-do-internet-forums-tend-to-prohibit-responding-to-inactive-threads"](see the link for the full discussion)
A necropost is a message that revives (as in necromancy) an arbitrarily old thread, causing it to appear above newer and more active threads. This practice is generally seen as a breach of etiquette on most forums. Because old threads are not usually locked from further posting, necroposting is common for newer users and in cases where the date of previous posts is not apparent.

[B]As posts are primarly ordered by recent activity, it can be annoying[/B] (irrelevant contributions make a post come to the top) when there are no levels (answers vs comments) of contributions. In Stack Exchange only when new questions, new answers, or modifications to any of the two are made, the "post" is brought to the top.
[/QUOTE]

The next one came up just recently - and I know that they are probably also have an attack of robots (even though unlike us, they have a filter in place already - "only users with recent PG work credit can post". We don't have that automatic protection option: MF users are not linked to GIMPS credit.)
[QUOTE="http://www.primegrid.com/forum_thread.php?id=8478"]Effective immediately, forum threads will be automatically locked one year after the most recent post. If a thread has been inactive for a year, it's better to start a new thread than to reactivate a moribund thread.

If you need to reference something in the old thread, you can always link to the original post or thread using the
/forum-specific/
tag.[/QUOTE]

retina 2019-02-28 21:34

[QUOTE=Batalov;509705]Glad you asked!

Most forums do (or recommend) this by default:


The next one came up just recently - and I know that they are probably also have an attack of robots (even though unlike us, they have a filter in place already - "only users with recent PG work credit can post". We don't have that automatic protection option: MF users are not linked to GIMPS credit.)[/QUOTE]I don't see those sites a relevant to this one. If someone has relevant information to a thread then just add it to the end. Better there than a new thread with no context. Many old threads still have important/interesting information and background. Abandoning them just because they are "old" is a poor criterion IMO.

Spammers are a separate issue. If we have one then ban them. New topic or old topic, it won't matter to a spammer.

Batalov 2019-02-28 21:46

[QUOTE=retina;509706]I don't see those sites a relevant to this one. ...Spammers are a separate issue. If we have one then ban them. New topic or old topic, it won't matter to a spammer.[/QUOTE]
You contradict yourself - right there.

"New topic or old topic, " ... the damage has already been done! You (as a user) go in to read some interesting discussions and at the top you see threads at the top:
[LIST][*][B]Record probable prime found![/B]
[*][B]The probable primes[/B] in Five-or-Bust
[*][B]Record 73-digit factor is found by user...[/B][/LIST]
and open them - only to find that they were :poop:-posted to float up.

Also I have a distinct feeling that you didn't read what I wrote entirely. - [url]https://communitybuilding.stackexchange.com/questions/2632/why-do-internet-forums-tend-to-prohibit-responding-to-inactive-threads[/url]
[B](see the link for the full discussion) [/B]
There you would have found:
[QUOTE]I've been a moderator on several pretty active forums, and I can offer a few reasons:

[B]It shifts focus away from new posts.[/B]

This is probably the number one reason. Most active users sort posts by date so that the new posts go to the top. This allows users to focus on questions and discussions as they come in. Posting to an old thread "bumps" the old thread to the top, which shifts our focus away from new posts to old posts. That might not be a big deal, except:
[B]
Most old posts have been abandoned.[/B]

Most threads are from new users, mostly with a specific question. That question is then either answered, or it's not answered and some time goes by and the user abandons the question.

Many "bumping" posts are answers to questions that have either already been answered or have been abandoned. If the OP hasn't visited the forum in a year, why spend time answering it? Why make other people spend time reading your post?

[B]It makes old threads harder to read.[/B]

Let's say a thread starts, then is abandoned for a year, then you make a post, some discussion ensues, and then another year goes by. Now I as a reader stumble across the thread. The actual answer that was originally in the thread is now somewhere in the middle of the discussion instead of at the bottom. I now have to figure out when each post was made, when the answer was posted, what happened after that, etc. It would be much better for me if this had been split into two separate threads.

[B]This can trigger discussions on abandoned threads.[/B]

Another thing I see very often is that one "bumping" post will cause the thread to rise to the top, which will cause other users to jump in, not realizing that the OP is long gone, and continue a discussion that has long since been abandoned. This creates a bit of a snowball effect as more active users spend time in that thread instead of on actual new conversations.

This might not be an issue if the discussion is actually interesting, but most of the time it's not.

[B]Most bumping posts are low quality.[/B]

Maybe your bumping post really does add something interesting, and maybe it does spark an interesting conversation. But 95% of the time it's a drive-by hit from a Google search, either offering a solution to an old problem (see above) or saying "thanks me too!" (notice that Stack Overflow disallows posts like this) or saying "I have the same problem, did you ever fix this?"

Those types of posts might be useful to you as a poster, but they aren't useful to the forum as a whole, and they especially aren't useful to power users who are policing the forum.

[B]It's hard to decide whether you're an exception to the rule.[/B]

Considering that 95% of bumping posts are low quality, it can be "hard" or time-consuming to take the time to read your post and the thread you've bumped to decide whether your post belongs there or not, then to reply to you asking you to start your own thread, or to lock the thread, or to take whatever action is now required of us.

[B]Most necromancing posts belong in their own thread.[/B]

If you think that your post would be useful, maybe because you're having a similar problem and the posted solutions didn't work for you, then your post belongs in a new thread. Instead of continuing the old discussion, start a new discussion and link to the old one.

This avoids all of the problems above, but allows you to ask follow-up questions or start a new discussion.

[B]Our time is free, but it's not worthless.[/B]

Keep in mind that you aren't just talking to the OP. You're talking to everybody on the forum, particularly "power users" who sort by date. They're all going to read your post. They're probably going to re-read the entire thread.

That might not seem like a lot of work, but keep in mind that many of these users are also moderating the forum, deleting spam (so much spam), banning rude users, answering questions, etc. We do this for free, in our spare time. You might think "what's the big deal if I make you spend a few minutes re-reading a thread", but moderating a forum is a zero-sum game. I only have a certain amount of time to do all this stuff. The more time you make me spend on old threads is less time I can spend banning spammers. So the more time you take away from us by bumping old threads, the less time we have to actually do our "jobs" on the forum.

Especially because the fix is easy. Just post a new thread with a link to the old one.

I know that some (or maybe all) of these issues can be addressed with different forum software. I really like Discourse, although it suffers from some of the same issues. And I know there are exceptions to all of the above. But if you're asking why forums (specifically the power users on those forums) frown on bumping old threads, these are some of the reasons why.[/QUOTE]

retina 2019-02-28 22:12

[QUOTE=Batalov;509708]You contradict yourself - right there.

"New topic or old topic, " ... the damage has already been done! You (as a user) go in to read some interesting discussions and at the top you see threads at the top:
[LIST][*][B]Record probable prime found![/B]
[*][B]The probable primes[/B] in Five-or-Bust
[*][B]Record 73-digit factor is found by user...[/B][/LIST]
and open them - only to find that they were :poop:-posted to float up.

Also I have a distinct feeling that you didn't read what I wrote entirely. - [url]https://communitybuilding.stackexchange.com/questions/2632/why-do-internet-forums-tend-to-prohibit-responding-to-inactive-threads[/url]
[B](see the link for the full discussion) [/B]
There you would have found:[/QUOTE]Your appeal to authority aside, I don't see how a spammer is related to the new/old threads. Entirely separate issue. And a lot of that dissertation you copied here seems to assume a post into an old topic automatically won't be relevant or be :poop:, but we have intelligent users here and adding new information can be useful on occasion.

Someone can start a new topic with :poop: also, how does that suddenly make it better in a new topic? People still have to open it to judge it's worth, just the same as with an "old" topic. I don't see what problem is being solved by this.

Batalov 2019-02-28 22:35

New threads started by a new user are, of course, preferred. You are immediately seeing what you will be getting by reading the thread -- before reading the thread.

[B]Our time is free, but it's not worthless.[/B]

paulunderwood 2019-03-01 01:27

[QUOTE=bbb120;509660]2887148238050771212671429597130393991977609459279722700926516024197432\
3037991527331163289831446392259419778031109293496555784189494417409338\
0561511397999942154241693397290542371100275104208013496673175515285922\
6962916775325475044445856101949404200039904432116776619949629539250452\
6987193290703735640322737012784538991261203092448414947289768854060249\
76768122077071687938121709811322297802059565867
this 397 digits composite number pass the miller rabin test base from 2 to 306,
so you should use at least one lucas test on probable prime ![/QUOTE]

Interesting. Many packages rely solely on M-R, e.g. GMP and can be so fooled. With a small cluster it is possible to construct such composites and break cryptosystems. The wise implementers use a Lucas PRP test too.

Dr Sardonicus 2019-03-01 13:35

[QUOTE=paulunderwood;509729]Interesting. Many packages rely solely on M-R, e.g. GMP and can be so fooled. With a small cluster it is possible to construct such composites and break cryptosystems. The wise implementers use a Lucas PRP test too.[/QUOTE]
The January 1995 paper [url=https://www.jointmathematicsmeetings.org/mcom/1995-64-209/S0025-5718-1995-1260124-2/S0025-5718-1995-1260124-2.pdf]RABIN-MILLER PRIMALITY TEST: COMPOSITE NUMBERS WHICH PASS IT[/url] gives a 337-digit composite which "passes" RM for all prime bases less than 200. It subsequently says[quote]The only limitation towards finding strong pseudoprimes to more bases in this way seems to be the difficulty of doing computations involving such large numbers.[/quote]So finding a number that "fools" RM for prime bases up to 300 is not terribly surprising.

IIRC there's a paper showing that a quadratic PRP test delivers something like nine times the bang as the RM test, for four times the bucks.

I checked the 397-digit number n in Pari-GP; first, ispseudoprime(n) gave 0 (composite). Then, ispseudoprime(n, 1) [RM with 1 base] gave 1 (PRP), but ispseudoprime(n,2) [RM tests with 2 "randomly selected" bases] gave 0 (composite).

paulunderwood 2019-03-01 15:31

There is a slight computational overhead for using larger bases (b) in M-R, since in left-right exponentiation we repeatedly calculate:

s*s mod n
s*b mod n if bit is 1

kriesel 2019-03-04 17:23

[QUOTE=retina;509685]Why is it necessary to start a new topic? I haven't seen anything on this board that disallows responding to an existing topic with pertinent information.[/QUOTE]Amen to that. I find it useful to have the history of, say CUDALucas development, or gpuowl, nearly all in one thread each, daunting though it may be to read through it all. Launching a new thread at the drop of a hat, scattered all over the haystack of thousands of threads, makes getting an overall picture of a given application more challenging, and can create an annoying amount of clutter.

Granted, there are other considerations, per uncwilly for example.
There may be about as many perspectives on some of the possible tradeoffs as there are participants.

R. Gerbicz 2019-03-04 19:53

[QUOTE=paulunderwood;509775]There is a slight computational overhead for using larger bases (b) in M-R, since in left-right exponentiation we repeatedly calculate:

s*s mod n
s*b mod n if bit is 1[/QUOTE]

You can almost hide that cost, see for example: [url]https://en.wikipedia.org/wiki/Exponentiation_by_squaring#Sliding_window_method[/url]
The fast gmp is also using this technique.

paulunderwood 2019-03-04 20:44

[QUOTE=R. Gerbicz;510120]You can almost hide that cost, see for example: [url]https://en.wikipedia.org/wiki/Exponentiation_by_squaring#Sliding_window_method[/url]
The fast gmp is also using this technique.[/QUOTE]

I recall this method... for example: N=(1001111011)_2 can be written as (10[10000-1][100-1])_2. The former takes 9S + 6M and the latter takes 9S + 2M +2D (where S=squaring, M=mult by base and D=div by base). I don't think I have it quite right :blush:

R. Gerbicz 2019-03-04 22:05

[QUOTE=paulunderwood;510124]I recall this method... for example: N=(1001111011)_2 can be written as (10[10000-1][100-1])_2. The former takes 9S + 6M and the latter takes 9S + 2M +2D (where S=squaring, M=mult by base and D=div by base). I don't think I have it quite right :blush:[/QUOTE]

No.

Say you are using k=3 in the method (k depends on length of the exponent),
then precompute x^3,x^5,x^7 mod n

See your N=(1001111011)_2 exponent

with 5 squaring get x^32, at this point you have processed the 100000_2 part in the exponent.
Now multiple this by x^(111_2)=x^7 to get x^39.
With 3 more squaring you get x^312.
Multiple this by x^(101_2)=x^5 to get x^317
With one more squaring you get x^634,
multiple this by x^(1_2)=x^1 to get x^635=x^N mod n. (all above computations are done in mod n).

If the length of the exponent is L, then with random exponent you need L squaring and only approx L/4 multiplication,
what is a good gain over the extra cost's standard L/2 multiplication (because half of the digits is 1).

Ofcourse there is an optimal k value for L, but the size of memory could also limit this k value (you need to store x^3 mod n,.. in the array). Also notice that you need 2^(k-1) multiplications to build up the precomputed array.


All times are UTC. The time now is 23:22.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.