Beautiful, James. This is great. 100,000 rows is pretty nice, too.

Just to be clear, I didn't want my of my slight frustration directed at you. I was just having a hard time getting my point across but you got it perfectly.

(the result is interesting when simple-text only isn't checked: the report.txt can be renamed to .html and it generates the table nice and pwetty)


If you're thinking of taking this further for TF or whatever, be my guest but this is all I was asking for.

Having the 'Factor=N/A," at the start is helpful. Having the two commas after the current bit level is good because it makes it easy to find-and-replace if that's the path one wants to take. Having ",xx," would be one step better still. Having a space to enter the desired level is truly above and beyond.

Definite no on defaulting to bit-level+1 because not all of the exponents in the list are necessarily factored to the same level to start.


That's all I can think of, but everything so far is exactly what I was after and there are easy ways of doing the rest.

[QUOTE=LaurV;381480]Filling it with "from 1 to 10000" returns nothing.[/quote]Fixed, thanks.

[QUOTE=LaurV;381480]Now, if we are at it, (I mean you, James :razz:), can we have a "limited" number of rows for the "[URL="http://www.mersenne.org/results/default.php"]work done[/URL]" report?[/QUOTE]Sure, done.

[QUOTE=TheMawn;381481]the result is interesting when simple-text only isn't checked: the report.txt can be renamed to .html and it generates the table nice and pwetty[/QUOTE]Thanks, fixed -- it will now download as report.html if text-only is not checked. Proper MIME type now added too.

[QUOTE=TheMawn;381481]Having a space to enter the desired level is truly above and beyond.[/QUOTE]Enjoy the above-and-beyond. :smile:

[QUOTE=LaurV;381480]Now, if we are at it, (I mean you, James :razz:), can we have a "limited" number of rows for the "[URL="http://www.mersenne.org/results/default.php"]work done[/URL]" report? I mean, beside of "exponent range" boxes, just a "show last 100 results" box, where I can edit the 100, same as it is done for top producer lists? [/QUOTE]

Grrr. We lost my last update to this web page where the exponent is linked to the full report on the exponent.

What I really want is to display each LL result exponent in color. Red = known bad, yellow = suspect error code or mismatches another LL, green = known good, black = none of the above.

This will let me quickly see at a glance if a machine starts returning bad LL results.

[QUOTE=Prime95;381495]Grrr. We lost my last update to this web page where the exponent is linked to the full report on the exponent.[/QUOTE]Sorry George, I guess I missed re-mirroring my copy before making my changes. Do you have a local copy of your modified file? Please send it to me and I'll merge my changes and yours.

No problem, James. I fixed it on the server.

Beautiful! [URL="http://www.youtube.com/watch?v=e5WygWnzj3w"]Thanks a million[/URL] to both of you. I was wondering if my post didn't escape unobserved, I have this luck of posting at the end of the page just one minute before someone else (usually The Mawn :razz:) posts a new page, hehe...

About the colors, yes, that would be nice to have too, but it it not really necessary, as the matched/notmatched is not differentiated in the current report, it will require some new DB tricks/flag, etc....

[QUOTE=Prime95;381495]What I really want is to display each LL result exponent in color. Red = known bad, yellow = suspect error code or mismatches another LL, green = known good, black = none of the above.[/QUOTE]I'll leave that to you. After some experimenting I conclude I apparently haven't figured out either the database structure or how to properly do the query in MSSQL.

[QUOTE=LaurV;381514]I have this luck of posting at the end of the page just one minute before someone else (usually The Mawn :razz:) posts a new page, hehe...[/QUOTE]

It has a funny effect on me, because when I finish my post, it leaves me on the new page because that's where my post went. However, because your post is still "unread" (because I haven't actually seen it) when I hit "Go to First Unread" it brings me to yours, and then I see mine when I go to the next page.

Selectivity
 

[QUOTE=James Heinrich;381494]Enjoy the above-and-beyond. :smile:[/QUOTE]

These extensions now provide access to unassigned work via report_factoring_effort much more selective than assigning some work via manual_assignment.
The latter can't select by sought start levels, nor nominate a target level.
Isn't this a tiny bit unbalanced?

[QUOTE=snme2pm1;381604]These extensions now provide access to unassigned work via report_factoring_effort much more selective than assigning some work via manual_assignment.
The latter can't select by sought start levels, nor nominate a target level.
Isn't this a tiny bit unbalanced?[/QUOTE]I have just cleaned up the code for the manual-assignments page so it would now be easy to add some additional interface to solicit a TF bit range from the user, but for it to do anything the back-end get_assignment_within_range code would need to be updated, and that's in George's court. If he is willing to add additional optional parameters to filter by TF level then I could add that into the GUI.