[QUOTE=ET_;474088]I am actually doing PRP-CF and PRP-CF-D.

Do you think I should stop until things are settled?

Luigi[/QUOTE]

Yeah, it was only an issue with older Prime95 versions that sent their PRP results to the server in a way that resulted in (sometimes) a missing list of known factors used during the test.

New versions (as George mentioned) will send the results fine.

I uploaded two results.txt files through the manual testing page. Among them there is the twin result from this exponent:

[CODE]Manual testing 22268579 F-PM1 2017-12-23 19:32 0.0 Factor: 752894280511036848897308855040509839552636123889 / (P-1, B1=350000, B2=7000000, E=6) 0.8378
Manual testing 22268579 F-PM1 2017-12-23 19:32 0.0 Factor: 752894280511036848897308855040509839552636123889 / (P-1, B1=350000, B2=7000000, E=6)[/CODE]

unlike the other three factors that were uploaded in the same batch this twin result does not show up in the 'Current Progress | Recent Cleared' list, not when sorted on date/time stamp and not when sorted on exponent.
They do however show up correctly in the 'My Account | Results' page and therefore are correctly inserted into the database. Seems to be a report problem.

Probably an artifact of the way composite factors are handled.

Composite factors will be broken into their prime component, but a side effect is that while the prime factors are recorded, the result log shows the original result text with the composite factor so the [url=https://www.mersenne.org/report_exponent/?exp_lo=22268579&full=1]exponent detail page[/url] apparently shows the composite factor recorded twice. This is just a display artifact.

What I can't readily explain is why neither the prime nor composite factors, nor indeed that exponent at all, are shown on the [url=https://www.mersenne.org/report_recent_cleared/]recent cleared report[/url].

I have an automatic PRP assignment that seems to have expired in error. The CPU is set to get PRP-100M automatically for one worker, which it did.

[URL="https://www.mersenne.org/report_exponent/?exp_lo=332291569&full=1"]https://www.mersenne.org/report_exponent/?exp_lo=332291569&full=1[/URL]

2017-12-28 Assigned
2018-01-10 P1 results returned
2018-01-10 Expired

It is still in my local work-to-do for the remaining PRP work.

[QUOTE=potonono;477195]I have an automatic PRP assignment that seems to have expired in error. The CPU is set to get PRP-100M automatically for one worker, which it did.

[URL="https://www.mersenne.org/report_exponent/?exp_lo=332291569&full=1"]https://www.mersenne.org/report_exponent/?exp_lo=332291569&full=1[/URL]

2017-12-28 Assigned
2018-01-10 P1 results returned
2018-01-10 Expired

It is still in my local work-to-do for the remaining PRP work.[/QUOTE]

Fixed. The P-1 result erroneously unassigned the exponent.

You should have the assignment back now.

It seems the first time checks category 0 threshold is stuck at 76737764 on the Assignment Rules page. This means there are only 10 category 0 LL assignments instead of 200.

Jacob

[QUOTE=S485122;477426]It seems the first time checks category 0 threshold is stuck at 76737764 on the Assignment Rules page. This means there are only 10 category 0 LL assignments instead of 200.

Jacob[/QUOTE]

I count 11. You are probably not counting my "hidden" cat 0 ([url=https://www.mersenne.org/M76722991]M76722991[/url])

[QUOTE=S485122;477426]It seems the first time checks category 0 threshold is stuck at 76737764 on the Assignment Rules page. This means there are only 10 category 0 LL assignments instead of 200.

Jacob[/QUOTE]

Fixed. The stored procedure was not recognizing exponents where a PRP result had been turned in.

I'm not sure why, but a user recently ran a PRP test (not a PRP cofactor test) on an already-factored small exponent: [M]M3,859,447[/M].

I think the server rejects LL residue results for already-factored exponents? If so, then probably the behavior should be consistent between LL results and PRP results.

PS,
The same user also ran a PRP test for a very similar exponent ([M]M3,859,477[/M]) which doesn't have known factors, but did already have two matching LL tests. Probably this type of result should be accepted by the server, as it was, but it's an unverified result that doesn't need verification, similar to those few exponents in the 75M range (like [M]M75,512,069[/M]) where we inadvertently ended up with two matching PRP tests and an unverified LL test. I presume the server already handles this situation and won't automatically assign a double-check on the superfluous test type?

On the page [URL="https://www.mersenne.org/report_recent_cleared/"]https://www.mersenne.org/report_recent_cleared/[/URL] the column 'Result' has been changed to include not just the result itself but also the method how it was obtained.

I have two suggestions.

A. Make the page wider, we now have only half the width of the screen in use and double lines because of the extra information not fitting in the cell.
B. Put the additional info on the method used in a separate cell so that automated use in spreadsheets and programs can use the results without having to undo the cell of the additional info.