![]() |
![]() |
#34 | |
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest
2×3×13×83 Posts |
![]() Quote:
Last fiddled with by kriesel on 2021-10-14 at 15:13 |
|
![]() |
![]() |
![]() |
#35 |
Sep 2009
13×179 Posts |
![]() |
![]() |
![]() |
![]() |
#36 |
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest
647410 Posts |
![]()
Stake your claims.
|
![]() |
![]() |
![]() |
#37 |
Xebeche
Apr 2019
๐บ๐๐บ
1BD16 Posts |
![]()
My prediction for Mp#49*, M(74 207 281) was March 08, 2025.
https://mersenneforum.org/showthread...619#post589619 You marked my prediction in your PDF file as 2028-03-08. It is incorrect. It should be 2025-03-08. |
![]() |
![]() |
![]() |
#38 |
Xebeche
Apr 2019
๐บ๐๐บ
1BD16 Posts |
![]()
Also, you have specified your forecast for Mp#49*, M(74 207 281) with the date 2021-08-26 and link:
https://www.mersenneforum.org/showpo...5&postcount=11 But I did not find such a forecast there. I have seen the forecast 2025-01-18 in attached PDF there but it dated by 10/13/2021 and not by 2021-08-26. It seems to me better to be more careful with numbers. Last fiddled with by greenskull on 2021-10-16 at 21:42 |
![]() |
![]() |
![]() |
#39 | ||
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest
145128 Posts |
![]() Quote:
Quote:
1) https://www.mersenneforum.org/showpo...5&postcount=11 is a reference post originated 2018-12-16, 12:03, that has been regularly updated numerous times over the years following, and (relative to now) was last updated 2021-10-13 at 12:45 (my time zone). The page 5 was added to one of the attachments updated, at a previous update, so page 5 got first posted there 2021-08-26. 2) The post date of an estimate does not change. It is an estimate's first appearance that counts, not any other time it gets reposted or mentioned, or remains in an updated post. (Read the rules, again.) 3) The update that added page 5 and multiple estimate computations was demonstrably after 2021-08-16, at which point only Mp#48* occupied page 5: see the attachment of https://mersenneforum.org/showpost.p...postcount=3436. 4) The date I saw and took note of on the previous version of the pdf on my server before generating the 2021-10-13 update pdf for updating was 2021-08-26. 5) Also https://mersenneforum.org/showpost.p...&postcount=128 posted 2021-10-06 makes explicit reference to the 2021-08-26 update with a link. "Projections for Mp#49*-51* were previously posted 2021-08-26 and you were notified of that." 6) Also, I update https://www.mersenneforum.org/showpo...5&postcount=11 when a milestone is reached. A previous milestone was reaching 57M DC completion, which https://www.mersenne.org/report_milestones/ shows as "2021-08-26 All tests below 57 million verified." 7) Another update would have been triggered by https://www.mersenne.org/report_milestones/ "2021-10-07 All exponents below 105 million tested at least once." 8) The next update would have been triggered by https://www.mersenne.org/report_milestones/ "2021-10-13 All tests below 58 million verified." 9) Whichever minor milestone is reached next, for which I then post an update of https://www.mersenneforum.org/showpo...5&postcount=11, will also change its modified-date. Which will also have nothing to do with when the Mp#49*-Mp#51* estimates were first posted. 10) Unfortunately we can not further confirm that 2021-08-26 date with the wayback machine, because archive.org does not have anything for that URL. It only does top level of mersenneforum.org, not individual posts. Even the data subforum comes up empty: http://web.archive.org/web/202108261...splay.php?f=21 11) Page 5 describes the fit on which the Mp#49*-Mp#51* estimates were computed. That fit is based on data for milestones occurring 2010-2020. Updating milestones data progress of 2021 or later has no effect on that. 12) There is no connection between the spreadsheet cells concerning 2021 milestones reached, and the estimate computations for Mp#49*-Mp#51*. The estimates computed on page 5 of the attachment are not and will not be changed by future updates of the earlier pages. Please stop posting false claims and faulty reasoning. The 2021-08-26 date corresponds to reality. Your false claim 2021-10-13 does not. Last fiddled with by kriesel on 2021-10-17 at 01:26 |
||
![]() |
![]() |
![]() |
#40 | ||
Xebeche
Apr 2019
๐บ๐๐บ
5×89 Posts |
![]()
I know very well what I am talking about :)
Your formula for estimating the quality of a participant's forecast uses the date that the forecast was made right? And the rating of participant's forecast depends on it. The earlier forecast date gives an advantage. Quote:
It can't be clearly verified and confirmed. 1) Ok. 2) Ok. 3) There is no forecast for Mp#49*, there is an approximate estimate of the year. 4) Do I just need to trust you, or can I see it somehow? 5) This post links to another post that has your prediction dated 10/13/2021. 6) Duplicates point 5) 7) Not directly related to the question. 8) Not directly related to the question. 9) Any bet must be documented. You cannot appeal to something that cannot be verified or confirmed. 10) ยฏ\_(ใ)_/ยฏ, no link - no bet. 11) Not directly related to the question. 12) Not directly related to the question. Quote:
What is the fallacy of this claim? If you cannot clearly confirm this date 2021-08-26, then you have to accept the date of your attached file (10/13/2021) where this your forecast is mentioned and anyone can see it. Then there will be more clarity. I thank you for correcting my forecast soon. But taking into account the fact that you are easily confusing (changing?) numbers as in my forecast, I cannot agree with the date 2021-08-26 of your forecast, which you cannot confirm in any way. Sorry :) Last fiddled with by greenskull on 2021-10-17 at 09:37 |
||
![]() |
![]() |
![]() |
#41 | |
Xebeche
Apr 2019
๐บ๐๐บ
5·89 Posts |
![]()
And further.
In your rules for evaluating predictions, we cannot adjust our earlier predictions and make new bets. Quote:
It may happen that within six months the fact deviates from the predicted trajectory and it becomes obvious that the forecast of one or another participant will not work even close. Such a participant will have no choice but to yearn for the rest of the time - for several years, without having the opportunity to cheerfully continue to participate in the game. Earlier, I proposed a slightly different system that allows as many predictions from the participants as they want. And this system also objectively assesses their talent for forecasting. And this system allows the participants to correct their forecasts on the way to Moment of Truth and make new bets. And the result (Diviner Talent Rate) will take into account all the attempts. https://www.mersenneforum.org/showth...848#post585848 You once said that it is all for fun. So let's change the system to the one I suggested so that it is really fun for everyone right down to the Moment of Truth. The 30.99999 days amendment can also be taken into account. Last fiddled with by greenskull on 2021-10-17 at 10:13 |
|
![]() |
![]() |
![]() |
#42 | |
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest
2·3·13·83 Posts |
![]() Quote:
I did not find a cached copy of GIMPS minor milestone progress versus year https://www.mersenneforum.org/showpo...5&postcount=11 in my web browser cache, downloads folder, on my server drive, etc. But I did find a copy of "gimps progress and rate.pdf" from the 2021-08-26 update of that page. It has been copied and renamed to preserve it on my server drive. The milestone progress post will be updated shortly. The actual posting date is shown by multiple methods to have been 2021-08-26. Greenskull's false claim of 2021-10-13 is refuted. Last fiddled with by kriesel on 2021-10-17 at 21:45 Reason: remove firefox's extra line feeds, correct second attachment, removed and readded 3rd & 4th to preserve order |
|
![]() |
![]() |
![]() |
#43 |
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest
194A16 Posts |
![]()
Effective as of the time and date of this post, these rules are appended to those posted at https://mersenneforum.org/showpost.p...&postcount=36:
12) Any of the following shall constitute grounds for disqualification of a participant:
14) There is no mechanism for appeal of disqualification. Disqualification is final. Disqualification is permanent. 15) Estimates made, without specification for each estimate, of all 3 of the following elements,
(Examples of credible basis are fits to past milestones, projections based on number of verification completions per day, projections based upon total GHzD required and primenet statistics, other fully documented math based approaches; examples of not credible basis are crystal balls, ouija boards, magic 8balls, dreams, premonitions, psychics) 16) Purpose is to identify a variety of alternate estimation methods, and demonstrate by test over extended periods, which are more effective or less effective. 17) Participation after the time and date of this post constitutes consent to the rules. (Anyone may of course start their own game, contest, whatever, spending the effort to: develop and post rules; tabulate estimates; upon completion of a verification, compute standings; etc. A different forum thread for such an undertaking is highly recommended.) Amen to that. |
![]() |
![]() |
![]() |
#44 |
Xebeche
Apr 2019
๐บ๐๐บ
5×89 Posts |
![]()
I don't want to participate in Kriesel's game.
Due to boring uninteresting rules and sloppy data handling. But I will stay here and will, from time to time, refine my predictions. If necessary, of course. Also, if someone wants to clarify theirs, then I will take this into account in my quality assessment system. I will apply the assessment I presented earlier here: https://www.mersenneforum.org/showth...848#post585848 A little later, I will summarize all the forecasts here in a table and publish. Last fiddled with by greenskull on 2021-10-17 at 21:55 |
![]() |
![]() |
![]() |
Thread Tools | |
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
[Mission Accomplished] Let's finish primality verification through Mp#48*, M(57โ885โ161) | kriesel | Marin's Mersenne-aries | 136 | 2021-11-02 04:40 |
Verification of Feitsma's psp(2) data | Happy5214 | Computer Science & Computational Number Theory | 5 | 2021-03-31 12:36 |
TF NF verification proposal from R. Gerbicz | kriesel | News | 0 | 2019-02-24 15:47 |
Unsafe verification? | CuriousKit | PrimeNet | 13 | 2015-06-21 14:49 |
Doing more about LL test verification | jasong | Software | 13 | 2010-03-10 18:53 |