[QUOTE=gLauss;559989]Yes, but it doesn't show up on the top right in "Latest Primenet details". It isn't important, but to me it looks like a bug. And I assume there are not many numbers which have both LL/DC and PRP, so it could be an interesting edge case.[/QUOTE]I scanned through several numbers that have a PRP but no recheck. None show a value there.

[QUOTE=gLauss;559989]Yes, but it doesn't show up on the top right in "Latest Primenet details". It isn't important, but to me it looks like a bug. And I assume there are not many numbers which have both LL/DC and PRP, so it could be an interesting edge case.[/QUOTE]It's not an edge case, it's more some incomplete code from the switch-over from LL to PRP. I have added some code that was missing so the top box should contain the PRP residue (if present) in most cases now. However, it may in many cases show the masked residue and show "needs double-check" even if it has completed CERT. This is due to a current lack of data on the cert records on PrimeNet -- you'll notice that the cert results show a message of "n/a" instead of the unmasked residue (it's a known problem with a complex, not-yet-devised solution, Aaron will need to fix it eventually but he's very busy these recent months). PrimeNet does display the unmasked residue after the certification but this data is not currently available to mersenne.ca. It will be fixed eventually, but that's beyond my control at the moment.

The part that is in my control, to wit showing the PRP residue (albeit masked) at the top of the page, has been fixed. Thanks for reporting.

[QUOTE=James Heinrich;560007]The part that is in my control, to wit showing the PRP residue (albeit masked) at the top of the page, has been fixed. Thanks for reporting.[/QUOTE]

[URL="https://www.mersenne.ca/exponent/10000271"]M10000271[/URL] - not quite correct code, PRP residue is not what it should be. See for yourself.

[QUOTE=Viliam Furik;560077][URL="https://www.mersenne.ca/exponent/10000271"]M10000271[/URL] - not quite correct code, PRP residue is not what it should be. See for yourself.[/QUOTE]Thanks, I'd (mostly) accounted for those but missed one place. Should be fixed now.

Another day, another trouble. The 'worst' pm1 page continue to display [URL="https://www.mersenne.ca/exponent/30218137"]M30,218,137[/URL]
only having a B1=435000 and no stage 2 while it is aware of the 'new' pm1 work done.
Also who is Architect Cubed? there is new pm1 done between [URL="https://www.mersenne.ca/exponent/30218137"]M30,218,137[/URL] and [URL="https://www.mersenne.ca/exponent/30272233"]M30,272,233
[/URL]

[QUOTE=firejuggler;560100]Another day, another trouble. The 'worst' pm1 page continue to display [URL="https://www.mersenne.ca/exponent/30218137"]M30,218,137[/URL] only having a B1=435000 and no stage 2 while it is aware of the 'new' pm1 work done.[/quote]You looked in that time window between importing new data from PrimeNet and regenerating the worst-PM1 database. But you raise a good point, starting tomorrow the import process will now immediately remove entries from the pm1_worst table if a new P-1 effort on that exponent is detected. It is of course possible that the new P-1 effort would still be poor and the exponent may still qualify for inclusion on the next rebuild, but it should prevent the situation you encountered.

[QUOTE=firejuggler;560100]Also who is Architect Cubed?[/QUOTE]Chris, aka [url=https://www.mersenneforum.org/member.php?u=144][i]chalsall[/i][/url], of GPU72 fame.

mersenne.ca/mfaktc.php is extremely unresponsive, takes too long to load data (about 30 seconds!) And starts all over again when sorting the table by some other column than the default one.

My side should be OK - Ryzen 9 3900X, 1 Gb/s download. CPU usage 5% (Prime95 is turned off for now. Don't anybody tell me I am wasting cycles, I know it :cry:)

-------
EDIT:
All of a sudden it's only about 1 second. Probably a temporary problem.

Hm... around 2-3 seconds for me, Ryzen 3800X, while running Prime95. :razz:

Browser is Chrome 88.0.4297.0 (Canary).

Edit: Did not saw your edit in time.

There's a small bug (most likely due to copy-paste of code) that causes [url]https://www.mersenne.ca/userfactors/ecm[/url] and [url]https://www.mersenne.ca/userfactors/any[/url] to display apparently the exactly same page (including links) as [url]https://www.mersenne.ca/userfactors/pm1[/url].

Not a copy-paste error, rather an unhandled entry in .htaccess
But either way, the error was there and now it's fixed, thanks for reporting! :smile:

Found factor not displayed in TF Results table
 

I wonder why for [URL="https://www.mersenne.ca/exponent/102796261"]M102796261[/URL] the found factor is displayed under the factors section but not in the Trial Factoring Results table together with the entry for 75-76 bits like e.g. for [URL="https://www.mersenne.ca/exponent/111954527"]M111954527[/URL].