Features request?

[Madpoo]

Originally Posted by James Heinrich

...
I have also discovered a problem that may be related to that. I have fixed the code, unfortunately I need to reparse a large amount of data. Hopefully I can complete that before the end of today, we'll see how it goes.

As George had mentioned, if it would be any faster to run certain queries on Primenet itself, let me know.

[James Heinrich]

Originally Posted by Madpoo

As George had mentioned, if it would be any faster to run certain queries on Primenet itself, let me know.

No, I think it's all good in that department. It's just a matter of bringing my data into full sync with PrimeNet, and once full sync is established then all the daily changes should be parsed from the daily XML dumps and things should (in theory) stay in sync.

I've readjusted all the no-factor TF levels, I'm currently sync'ing B1/B2 PM1 bounds, and I still need to check for any exponents that PrimeNet thinks are factored by my database doesn't know about. Once that's all done I think it should be getting reasonably close.

[James Heinrich]

I have now finished sync'ing all the data I think I need to. So the numbers should be pretty close (keeping in mind my data is delayed 24h from PrimeNet).

[lycorn]

It´s looking nice now.
Thx a lot for your work!

[manfred4]

Great Job! Finally having this tool again!

But there is one small thing that still bugs me a bit: if you Zoom in in some region like 300M and then zoom out again you have a table starting at 300M and ending at 1200M, not as I would think having 0M to 900M again.

Not found anything out of order datawise anymore, good job!

[James Heinrich]

Originally Posted by manfred4

But there is one small thing that still bugs me a bit: if you Zoom in in some region like 300M and then zoom out again you have a table starting at 300M and ending at 1200M, not as I would think having 0M to 900M again.

That is one issue I still need to address. Another is the data range zoomed to on mersenne.org when zooming in beyond the data I have.

[snme2pm1]

Originally Posted by James Heinrich

(keeping in mind my data is delayed 24h from PrimeNet).

Maybe at some convenient point, your schedule for that can be exposed for clarity.

Originally Posted by James Heinrich

the data range zoomed to on mersenne.org when zooming in beyond the data I have.

When in a mode of presenting purely recent numbers, why not use an agent at mersenne.org for a live tally, as George suggested?

At the moment, when using Control key with links, browsers are not opening a fresh tab.
Also I didn't try to work out what time zone mersenne.ca operates with for messages.
The red disclaimer patch you had some hours ago used a non-universal style of date, but was that UTC time or something else?
p.s. I wasn't suggesting a live tally across vast ranges at the high end of the space.

[James Heinrich]

Originally Posted by manfred4

But there is one small thing that still bugs me a bit: if you Zoom in in some region like 300M and then zoom out again you have a table starting at 300M and ending at 1200M, not as I would think having 0M to 900M again.

The behaviour should be more intuitive now.

Originally Posted by snme2pm1

Maybe at some convenient point, your schedule for that can be exposed for clarity.
Also I didn't try to work out what time zone mersenne.ca operates with for messages.

PrimeNet generates its daily XML dump at midnight UTC, completing within a couple minutes.
mersenne.ca currently checks for the XML dump at 00:27h, but with the caveat that the server actually runs in EDT timezone, with daylight-savings-time, so that would be 01:27h between November and April. However I have (now) set mersenne.ca to operate in UTC since that is what the timestamp data from PrimeNet is in. I have added a data-current-as-of date at the top of the table.

Originally Posted by snme2pm1

At the moment, when using Control key with links, browsers are not opening a fresh tab.

The range labels at the start of the rows are now <a href> links that can be ctrl-clicked, right-clicked and so forth as normal links; the bulk of the table row still has the onclick event for convenience.

[LaurV]

Originally Posted by James Heinrich

That is one issue I still need to address.

Or maybe not! I think is better as it is. Maybe I want to see the data from 2M to 12M, and leave apart the lower expos (this was just an example).

[James Heinrich]

Originally Posted by LaurV

Or maybe not! I think is better as it is. Maybe I want to see the data from 2M to 12M, and leave apart the lower expos (this was just an example).

You still can. The behaviour change I made affects the "zoom out" link. You can still go directly to view the range you want (2M-12M in your example), currently by fiddling the URL but I'll try and expose that to a more friendly GUI.

[LaurV]

Brilliant! I got it! I can use it till the interface is ready, you can make it low priority in the list.
A very well done job!

Waiting for the "change" reports hehe