[QUOTE=chalsall;539132]Hey all.

So, in my spare time I've been experimenting with the D3 Javascript graphing package. I thought some of you might be interested in one of the results...

If you click on the new links in the Range column in the [URL="https://www.gpu72.com/reports/available/"]available report[/URL], you'll be taken to a chart of the TF level of that 1M range. There are links from this page that lets you drill down to see all unfactored candidates, DC candidates, and those DC'ed but not factored.

For example, [URL="https://www.gpu72.com/charts/tf/dc/98/"]this chart of the 98M range[/URL] shows that almost all FC runs were done after TF'ing to 77.
[/QUOTE]

I don't understand these charts at all. What are the 0000 - 7400 running across the bottom and what are the colors?

[QUOTE=Chuck;539138]What are the 0000 - 7400 running across the bottom and what are the colors?[/QUOTE]

0.01M sub-ranges of the 1M range being viewed. I'll try to make that rendering clearer later.

Edit: Colors... Scroll your browser to the right. The key is in the upper-right-hand corner. Red == 72; Purple is 77.

[QUOTE=chalsall;539140]0.01M sub-ranges of the 1M range being viewed. I'll try to make that rendering clearer later.

Edit: Colors... Scroll your browser to the right. The key is in the upper-right-hand corner. Red == 72; Purple is 77.[/QUOTE]

That makes more sense as it goes from 0000 to 9900.

My Colab results are not being submitted automatically
 

Since Saturday night my Colab results have not been automatically submitted. I just did a manual submission of seven results.

[QUOTE=Chuck;539158]Since Saturday night my Colab results have not been automatically submitted. I just did a manual submission of seven results.[/QUOTE]

OK... The Primenet API is designed such that the Client has to exchange settings parameters every so often, or else the Primenet server will complain about accepting results.

I now know how long that time period is...

For those who started auto-submitting about a week ago, your "virtual" machine has checked in with Primenet, and all results are being autosubmitted again.

[QUOTE=chalsall;538894]a DNS lookup failure is the only possibility.
I've got a fall-back contingency worked out in my head, which I'll implement shortly.
But the good news is the code is sane (or, at least, not insane).[/QUOTE]I just fired up my 3 instances, and two started working normally but the third (actually the first one I started by a couple seconds) did not start nice. Instead of doing the selftest and exiting, it does the selftest and loops. And loops and loops. After some time I gave up and manually stopped/restarted it, but it kept looping through the selftest (display edited for brevity but it repeated the octet of output lines each time):[code]20200309_155258 ( 0:04): Installing needed packages
20200309_155303 ( 0:04): Fetching initial work...
20200309_155303 ( 0:04): Running GPU type Tesla P100-PCIE-16GB

20200309_155303 ( 0:04): running a simple selftest...
20200309_155308 ( 0:04): Selftest statistics
20200309_155308 ( 0:04): number of tests 107
20200309_155308 ( 0:04): successfull tests 107
20200309_155308 ( 0:04): selftest PASSED!
20200309_155308 ( 0:04): Fetching initial work...
20200309_155308 ( 0:04): Running GPU type Tesla P100-PCIE-16GB

20200309_155308 ( 0:04): running a simple selftest...
20200309_155314 ( 0:04): running a simple selftest...
20200309_155321 ( 0:04): running a simple selftest...
20200309_155329 ( 0:04): running a simple selftest...
20200309_155337 ( 0:04): running a simple selftest...
20200309_155345 ( 0:04): running a simple selftest...
20200309_155354 ( 0:05): running a simple selftest...
20200309_155402 ( 0:05): running a simple selftest...
20200309_155411 ( 0:05): running a simple selftest...
20200309_155419 ( 0:05): running a simple selftest...
20200309_155428 ( 0:05): running a simple selftest...
20200309_155437 ( 0:05): running a simple selftest...
20200309_155446 ( 0:05): running a simple selftest...
20200309_155454 ( 0:06): running a simple selftest...
20200309_155504 ( 0:06): running a simple selftest...
20200309_155513 ( 0:06): running a simple selftest...
20200309_155522 ( 0:06): running a simple selftest...
20200309_155531 ( 0:06): running a simple selftest...
20200309_155540 ( 0:06): running a simple selftest...
20200309_155550 ( 0:06): running a simple selftest...
20200309_155559 ( 0:07): running a simple selftest...
20200309_155608 ( 0:07): running a simple selftest...
20200309_155617 ( 0:07): running a simple selftest...
20200309_155626 ( 0:07): running a simple selftest...
20200309_155635 ( 0:07): running a simple selftest...
20200309_155644 ( 0:07): running a simple selftest...
20200309_155653 ( 0:08): running a simple selftest...
20200309_155702 ( 0:08): running a simple selftest...
20200309_155711 ( 0:08): running a simple selftest...
20200309_155721 ( 0:08): running a simple selftest...
20200309_155730 ( 0:08): running a simple selftest...
20200309_155739 ( 0:08): running a simple selftest...
20200309_155748 ( 0:08): running a simple selftest...
20200309_155758 ( 0:09): running a simple selftest...

Exiting...
Can't locate LWP/UserAgent.pm in @INC (you may need to install the LWP::UserAgent module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.1 /usr/local/share/perl/5.26.1 /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at ./comms.pl line 32.
BEGIN failed--compilation aborted at ./comms.pl line 32.
Done.[/code]Scroll down to the error at the end of the above dump, it may be relevant. It appeared when I aborted the session (clicked the "interrupt execution" button).

[QUOTE=James Heinrich;539218]Scroll down to the error at the end of the above dump, it may be relevant. It appeared when I aborted the session (clicked the "interrupt execution" button).[/QUOTE]

Thank you!!! Critical information.

I added the loop to the Bootstrap code, such that it would keep retrying the fetch. This was based on the theory that the problem was DNS lookup failure.

However, this indicates that instead, the problem is the "apt install" call isn't working for the needed Perl modules at the very beginning of the script.

So... For anyone who sees this type of behavior, please stop and rerun the Section. Cursing in my general direction is always an option as well...

Edit: OK, I've just "pushed" a new version of the Bootstrap payload (V0.421) which expands the loop such that the apt install is retried as well. Thanks, James; I never would have figured that out if you hadn't posted that bit of the output. My instances, of course, never exhibited this behaviour even though I'm running the exact same code.

[QUOTE=chalsall;539219]I've just "pushed" a new version of the Bootstrap payload (V0.421) which expands the loop such that the apt install is retried as well.[/QUOTE]Better :smile:

[code]20200309_173329 ( 0:05): GPU72 TF V0.421 Bootstrap starting (now with CPU support!)...
20200309_173329 ( 0:05): Working as "<redacted>"...

20200309_173329 ( 0:05): Installing needed packages
20200309_173335 ( 0:05): Fetching initial work...
20200309_173336 ( 0:05): Running GPU type Tesla K80

20200309_173336 ( 0:05): running a simple selftest...
20200309_173341 ( 0:05): Selftest statistics
20200309_173341 ( 0:05): number of tests 107
20200309_173341 ( 0:05): successfull tests 107
20200309_173341 ( 0:05): selftest PASSED!
20200309_173341 ( 0:05): Installing needed packages
20200309_173345 ( 0:05): Fetching initial work...
20200309_173346 ( 0:05): Running GPU type Tesla K80

20200309_173346 ( 0:05): running a simple selftest...
20200309_173353 ( 0:05): Selftest statistics
20200309_173353 ( 0:05): number of tests 107
20200309_173353 ( 0:05): successfull tests 107
20200309_173353 ( 0:05): selftest PASSED!
20200309_173353 ( 0:05): Installing needed packages
20200309_173413 ( 0:05): Fetching initial work...
20200309_173414 ( 0:05): Running GPU type Tesla K80

20200309_173414 ( 0:05): running a simple selftest...
20200309_173431 ( 0:06): Selftest statistics
20200309_173431 ( 0:06): number of tests 107
20200309_173431 ( 0:06): successfull tests 107
20200309_173431 ( 0:06): selftest PASSED!
20200309_173431 ( 0:06): Starting trial factoring M99845491 from 2^74 to 2^75 (38.32 GHz-days)

20200309_173431 ( 0:06): Exponent TF Level % Done ETA GHzD/D Itr Time | Class #, Seq # | #FCs | SieveRate | SieveP
20200309_173445 ( 0:06): 99845491 74 to 75 0.1% 2h22m 387.68 8.896s | 0/4620, 1/960 | 20.47G | 2301.6M/s | 82485[/code]Failed the first two times, but then caught and ran.

Isn't it fun to write code for things you can't actually test? :whee:

[QUOTE=James Heinrich;539224]Better :smile:

Failed the first two times, but then caught and ran.

Isn't it fun to write code for things you can't actually test? :whee:[/QUOTE]
I saw behaviour like this yesterday (I think while the code was in flux.

I noticed that there was a factor found by a P-1 instance that is on my GPU72 graph, but the one for the TF factor found within 24 hours of it is not on the graph. Both of theses are in the last 48 hours.

Result not needed
 

Thought I would pass this on, one of my GPU72 Colab assignments received a result not needed message from PrimeNet today when I reported it. [URL="https://www.mersenne.org/M107578847"]M107578847[/URL] (272-273).