The Factoring Report at mersenne.ca - Page 2

lycorn · 2016-02-27, 17:36

It was updated last night, but there is something wrong. Even the grand total of prime exponents between 1 and 1B is incorrect. Weird...

lycorn · 2016-03-17, 08:13

http://www.mersenne.ca/status/tf

... needs some love and care

.

Madpoo · 2016-03-17, 21:01

Quote:

Originally Posted by lycorn

http://www.mersenne.ca/status/tf

... needs some love and care

.

I hope it didn't break because of large #'s of new results (first 1000 out of 45000 "no factor by P-1") that were added yesterday.

Well... probably not? Yesterday's result archive is only slightly larger than the day before (830 KB versus 700 KB one day earlier).

Give James a chance to check it out I guess...hopefully nothing big.

Mark Rose · 2016-03-17, 21:06

I also dumped in close to 20,000 no factor lines.

lycorn · 2016-03-22, 13:03

Thanks mainly to monst´s efforts, the whole 700-800M range is now fully TFed to at least 70 bits!
Let´s see what comes next...

http://www.mersenne.ca/status/tf

lycorn · 2016-04-05, 12:13

http://www.mersenne.ca/status/tf

Broken again.

lycorn · 2016-06-28, 15:25

I´ve just noticed 4 exponents in the 300M range reported as being TFed to 66 bits in This report.

But, using the Primenet report available at Reports->Detailed Reports->Factoring Limits, I found that there aren´t any exponents still at 66 bits in the 300M range.
This is obviously not a big deal in itself, but it made me wonder why it happened, and whether other false infos may also be present in the reports.

Gordon · 2016-06-29, 08:08

Quote:

Originally Posted by lycorn

http://www.mersenne.ca/status/tf

Broken again.

Last 2 days of data are missing...

petrw1 · 2019-01-17, 17:05

...

petrw1 · 2019-01-17, 17:58

Quote:

I'm aware of problems but on vacation until 20 Jan, I have email-only access, can't post on forum and can't fix my server. Thanks :)

.

James Heinrich · 2019-01-21, 02:38

Data should be current again. A one-off malformed result caused a hangup in the import process.

2019-01-17, 17:05	#20
petrw1 1976 Toyota Corona years forever! "Wayne" Nov 2006 Saskatchewan, Canada 4676₁₀ Posts	2019-01-16 is AWOL ... Last fiddled with by petrw1 on 2019-01-17 at 17:12 Reason: Speling :)

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Mersenne.ca Status Report	Gordon	mersenne.ca	168	2018-06-17 22:48
Factoring Limit Report --> Assignment	0PolarBearsHere	PrimeNet	9	2015-12-09 08:15
Mersenne.ca Status Report	Gordon	mersenne.ca	1	2015-09-22 10:53
Mersenne statistics on p-1 factoring	diep	Factoring	10	2010-11-14 19:27
Mersenne NUmber Factoring	andi314	Math	4	2002-11-26 14:25

2016-02-27, 17:36	#12
lycorn Sep 2002 Oeiras, Portugal 2⁶×23 Posts	It was updated last night, but there is something wrong. Even the grand total of prime exponents between 1 and 1B is incorrect. Weird...

2016-03-17, 08:13	#13
lycorn Sep 2002 Oeiras, Portugal 2⁶×23 Posts	http://www.mersenne.ca/status/tf ... needs some love and care .

2016-03-17, 21:06	#15
Mark Rose "/X\(‘-‘)/X\" Jan 2013 2²×733 Posts	I also dumped in close to 20,000 no factor lines.

2016-03-22, 13:03	#16
lycorn Sep 2002 Oeiras, Portugal 1472₁₀ Posts	Thanks mainly to monst´s efforts, the whole 700-800M range is now fully TFed to at least 70 bits! Let´s see what comes next... http://www.mersenne.ca/status/tf

2016-04-05, 12:13	#17
lycorn Sep 2002 Oeiras, Portugal 2⁶·23 Posts	http://www.mersenne.ca/status/tf Broken again.

2016-06-28, 15:25	#18
lycorn Sep 2002 Oeiras, Portugal 2700₈ Posts	I´ve just noticed 4 exponents in the 300M range reported as being TFed to 66 bits in This report. But, using the Primenet report available at Reports->Detailed Reports->Factoring Limits, I found that there aren´t any exponents still at 66 bits in the 300M range. This is obviously not a big deal in itself, but it made me wonder why it happened, and whether other false infos may also be present in the reports.

2019-01-21, 02:38	#22
James Heinrich "James Heinrich" May 2004 ex-Northern Ontario 19×179 Posts	Data should be current again. A one-off malformed result caused a hangup in the import process.