[QUOTE=James Heinrich;549451]I have added some complexity and separated out the report generation into a separate job that will attempt to run 1-2 hours after the data import job, but it will check the factor queue and wait until all of yesterday's factors are processed before compiling the report.[/QUOTE]

Humans! Don't get me started about humans! (Paraphrasing Marvin the Martian. :wink:)

[QUOTE=chalsall;549458]Marvin[/QUOTE]

At first sight of "Marvin", I was thinking of Marvin the paranoid android.
That was a wonderful creation by the writer Douglas Adams.
I'm less familiar with that other Marvin.

A salute to James for taking the trouble to reschedule the processing of data.
I guess that I was confused about the processing steps that occur at mersenne.ca alone, rather than potential multiple data imports from mersenne.org.

Do Data for June 30.

[CODE]Displayed data as of 2020-06-30T23:59:59+00:00
Error: no data (unexpected?)[/CODE]

[QUOTE=petrw1;549501]Do Data for June 30.

[CODE]Displayed data as of 2020-06-30T23:59:59+00:00
Error: no data (unexpected?)[/CODE][/QUOTE]

Would you might like to say more about the origin of such exception message?

I suppose that that if James has made significant changes of routine, then there might have been something overlooked.
Yet I observed that he was awake not long ago at the time of any transitional arrangements.

[QUOTE=snme2pm1;549502]Would you might like to say more about the origin of such exception message?

I suppose that that if James has made significant changes of routine, then there might have been something overlooked.
Yet I observed that he was awake not long ago at the time of any transitional arrangements.[/QUOTE]

Here: [url]https://www.mersenne.ca/status/tf/0/0/1/2000[/url]

[QUOTE=petrw1;549507]Here: [url]https://www.mersenne.ca/status/tf/0/0/1/2000[/url][/QUOTE]

Crikey do we need to wake him again?

The new job ran fine, but inserted the data under the wrong date (2020-07-01 instead of 2020-06-30). I've moved the data over and (I think) corrected the problem that generated the incorrect date. We'll see tonight if it behaves as expected.

[QUOTE=James Heinrich;549528]The new job ran fine, but inserted the data under the wrong date (2020-07-01 instead of 2020-06-30). I've moved the data over and (I think) corrected the problem that generated the incorrect date. We'll see tonight if it behaves as expected.[/QUOTE]

I want to run a similar argument when my boss next complains.
No disrespect intended, yet I think of the idea when the surgeon states that the operation was successful, but the patient died.

Yeah details...
Thanks for doing a great job.

I have a feature request for mersenne.ca. Would it be possible to add average B1, B2 bounds for prior P-1 factorization attempts to the tables that list how far (in bit levels) that ranges have been trial-factored? Does anyone else believe this might be useful?

Could you point me to a sample URL of where you would like to see this?

[URL="https://www.mersenne.ca/status/tf/0/0/5/1400"]https://www.mersenne.ca/status/tf/0/0/5/1400[/URL]

Here is what I'm imagining: between the "unfactored" and "<69" columns there would be a B1 column and a B2 column. In the "14.00M" row of the B1 column, there would be the average B1 value (average over the 205 remaining unfactored candidates). Same thing for the B2 column. In the "Total" row, the average over all 2206 unfactored candidates (should be easy to calculate given previously calculated averages) would appear in the appropriate columns.

If it's too much work or others don't deem it important enough, I understand. Just spitballing here.