[QUOTE=LaurV;408606]Waiting for the "change" reports :razz: hehe[/QUOTE][url]http://www.mersenne.ca/status/tf/1/1/0[/url]

Illumination
 

[QUOTE=James Heinrich;408613][url]http://www.mersenne.ca/status/tf/1/1/0[/url][/QUOTE]
Thanks very much.

Something looks fishy
 

5.43M shows 65:1, 66:218 // mersenne.org says 65:0
5.44M shows 65:220, 66:219 // that's too many
At 2015-08-23 21:37, in 5.44M region I lodged 219 no factor, 1 factor
5.44M Differences suggest +219 unfactored. Is that supposed to be non-positive?

[QUOTE=James Heinrich;408613][URL]http://www.mersenne.ca/status/tf/1/1/0[/URL][/QUOTE]Yarrrr! :chappy:

[QUOTE=snme2pm1;408632]5.43M shows 65:1, 66:218 // mersenne.org says 65:0
5.44M shows 65:220, 66:219 // that's too many
At 2015-08-23 21:37, in 5.44M region I lodged 219 no factor, 1 factor[/QUOTE]My best guess at this point is that it's related to my server's asynchronous processing of the PrimeNet data and absorbing the day's newly discovered factors -- the TF level data is generated immediately upon import from PrimeNet but the TF-level table wasn't yet updated for the newly-discovered factors. I have changed that and tomorrow the numbers might match closer.

edit: now that the factors are absorbed, I re-ran today's numbers and at very quick glance it seems to look better? I'm sure someone will point out where it's not.

[QUOTE=James Heinrich;408642]I re-ran today's numbers and at very quick glance it seems to look better?[/QUOTE]
Yes.
Note that the factor in the 5.43M brick was lodged more than 22 hours before midnight:
5433577 F 2015-08-23 01:37
Strange that it wasn't settled after such a long time.

I noticed that around the 00:30 time, the presented pages advised the new day date, but not revised data.
Then I saw one page with revised data, and other requests time-out, until a few minutes later.

Huh?
 

[URL="http://www.mersenne.ca/status/tf/1/1/0"]http://www.mersenne.ca/status/tf/1/1/0[/URL]

[CODE]Notice: Undefined offset: 0 in /var/www/vhosts/mersenne.ca/httpdocs/visualization.php on line 125 Warning: Invalid argument supplied for foreach() in /var/www/vhosts/mersenne.ca/httpdocs/visualization.php on line 125 Data as of 2015-08-23T23:59:00+00:00
Notice: Undefined offset: 0 in /var/www/vhosts/mersenne.ca/httpdocs/visualization.php on line 188 Warning: Invalid argument supplied for foreach() in /var/www/vhosts/mersenne.ca/httpdocs/visualization.php on line 188 Notice: Undefined index: exponents in /var/www/vhosts/mersenne.ca/httpdocs/visualization.php on line 57[/CODE]

[QUOTE=snme2pm1;408646]Note that the factor in the 5.43M brick was lodged more than 22 hours before midnight:
Strange that it wasn't settled after such a long time.[/QUOTE]Sorry, perhaps I didn't explain well. PrimeNet runs an export job at 00hUTC (or a few seconds after) exporting all the data submitted on the date that just ended. About 25 minutes later I import that data into mersenne.ca. Since each day's data can contain several thousand factors and it takes about small but non-trivial amount of realtime to verify each factor, during the import I simply pass off all the day's submitted factors to my batch factor processing job, which chews on a few factors every minute or so and (eventually) imports all the data and updates the tables. This works very well, unfortunately in the case of this new report I need to have the factored-or-not flag set correctly in the exponents table [i]before[/i] generating the day's data, so when the PrimeNet data contains any factors I now immediately update that flag, although the factor processing is still done in the queue as before. As far as the site visitor goes, this means basically [U]nothing[/U], the above was just a babbling explanation for those who like such things.

[QUOTE=snme2pm1;408646]I noticed that around the 00:30 time, the presented pages advised the new day date, but not revised data.
Then I saw one page with revised data, and other requests time-out, until a few minutes later.[/QUOTE]Good observation. The data-date was being pulled from the table that's imported directly from PrimeNet so would show the new date as soon as the import was complete, but there would be about a half-hour window where the new data was imported, but not yet processed for the visualization table data. This is fixed now, the date is stored elsewhere and only updated once the visualization tables are updated.

[QUOTE=ric;408677]Notice: Undefined offset: 0[/QUOTE]I needed to fiddle some things around. It should be back to normal now.

[QUOTE=James Heinrich;408691]It should be back to normal now.[/QUOTE]

Well done! Thx

[QUOTE=LaurV;408606]I can use it till the interface is ready, you can make it low priority in the list.[/QUOTE]I've put a crude GUI up now, it'll need some refining later but it'll get you started.