Features request?

[snme2pm1]

Originally Posted by James Heinrich

Consider this alpha, I know there's glaring bugs so don't even worry about bug reports yet, please

Ok, so regarded.
Initial view showed some positive elements, and some numbers that were plainly incorrect, but nevertheless somewhat approximate.
But perhaps you know that, and perhaps I need not mention it.
Gosh, one of your quotes speaks about significant processing work (2 hours 55 min 23.28 sec), that's a scary burden for what ever that component was.
Hopefully there will not be a daily burden approaching that magnitude on any piece of equipment, or is that a misguided belief?
The response to requests during the past 24 hours has produced an exception message, and perhaps that is likewise known and similarly unmentionable.

[LaurV]

On the same direction as the previous poster...

Notice: Undefined offset: 0 in /var/www/vhosts/mersenne.ca/httpdocs/visualization.php on line 86 Warning: Invalid argument supplied for foreach() in /var/www/vhosts/mersenne.ca/httpdocs/visualization.php on line 86

[James Heinrich]

Originally Posted by snme2pm1

some numbers that were plainly incorrect, but nevertheless somewhat approximate.

Please give more details as to which numbers you saw as incorrect (and what you think they should be, and where you got the correct number from).

Originally Posted by snme2pm1

Hopefully there will not be a daily burden approaching that magnitude on any piece of equipment, or is that a misguided belief?

No, daily query is more like

Query OK, 16496 rows affected (2 min 38.99 sec)

Originally Posted by snme2pm1

The response to requests during the past 24 hours has produced an exception message

Apparently the aforementioned daily query didn't run like it was supposed to. I ran it manually just now, I'll need to investigate why it didn't run on schedule.

Please still consider it alpha, but you can start telling me about bugs now

[James Heinrich]

Originally Posted by snme2pm1

some numbers that were plainly incorrect, but nevertheless somewhat approximate.

Probably relevant: mersenne.ca is still chewing through a list of approx 700,000 factors that may or may not already be known to mersenne.ca (about 95% were not previously recorded). This processing will take at least another 2 days, and of course until that's done the number of known factors in any particular range is most likely inaccurate.

[chalsall]

Originally Posted by James Heinrich

Please still consider it alpha, but you can start telling me about bugs now

Looking good James! Thanks for taking this on!

Please let me know when you get the weekly deltas display implemented (I'm imagining in about a week... ) and I'll put back the links for the "Weekly Progress Reports" on GPU72.

[James Heinrich]

Originally Posted by chalsall

(I'm imagining in about a week... )

A week from now I'll be peregrinating the Kettle Valley far away from thoughts of Mersenne, so it'll likely be at least two weeks (the data is structured appropriately, but I haven't yet written anything to display interval-delta data. I'll let you know when it's working.

[manfred4]

Originally Posted by James Heinrich

Please give more details as to which numbers you saw as incorrect (and what you think they should be, and where you got the correct number from).

I thought the same - for example there are over 230k Exponents at 65 bits between 400M and 600M on here, whereas there should be none at all, see here.

But for the rest of it the look is really nice already ;)

[James Heinrich]

Originally Posted by manfred4

I thought the same - for example there are over 230k Exponents at 65 bits between 400M and 600M on here, whereas there should be none at all, see here

I'll wait until it's finished chewing on the unprocessed known factors before I take a closer look, although a quick glance suggests that alone is not sufficient to explain the difference.

Ideally when Aaron is back on the case I can get a 1-time export of all unfactored PrimeNet exponents and their TF level to bring my master table in sync with PrimeNet (all subsequent changes should be propagated correctly, but I likely have some historical inaccuracies).

[alpertron]

Excellent!!!

One small problem is that there is an extra row at the end. For instance if I want to see the range 0 to 1000M (see here), there is a row 1000M with data from 1000M to 1001M.

[James Heinrich]

Originally Posted by alpertron

One small problem is that there is an extra row at the end. For instance if I want to see the range 0 to 1000M (see here), there is a row 1000M with data from 1000M to 1001M.

Thanks, fixed.

[chalsall]

Originally Posted by James Heinrich

A week from now I'll be peregrinating the Kettle Valley...

Lucky man!

If you have the time, I highly recommend visiting Peachland. There are many unique wineries there as well.