Introducing tf1G.py v0.09:

In running the script, I noticed that the script counted all the lines in the results file when it ran the count_exponents_tested function. This is confirmed when I ran v0.08 on a Colab session: I got 703 tested, which is really 695 exponents plus 8 extra lines where mfaktc has printed: found 1 factor for Mxxxxxxxxxx. This has now been rectified: the function will only add lines which has the strings "no factor" or "found".
The script is attached below:

[QUOTE=Dylan14;532129]Introducing tf1G.py v0.09:

In running the script, I noticed that the script counted all the lines in the results file when it ran the count_exponents_tested function. This is confirmed when I ran v0.08 on a Colab session: I got 703 tested, which is really 695 exponents plus 8 extra lines where mfaktc has printed: found 1 factor for Mxxxxxxxxxx. This has now been rectified: the function will only add lines which has the strings "no factor" or "found".
The script is attached below:[/QUOTE]This should also allow for users modifying the mfaktx.ini file so that additional lines providing a date and time stamp are excluded from the exponent count. Or manual edits.

[QUOTE=kriesel;532130]This should also allow for users modifying the mfaktx.ini file so that additional lines providing a date and time stamp are excluded from the exponent count. Or manual edits.[/QUOTE]

As for the time stamp: the script only counts lines that have those strings that I mentioned. Since the time stamp looks something like this:

[CODE][Thu Dec 5 17:56:55 2019][/CODE]the script ignores it since those strings do not appear.
As for manual edits: would you mind providing some examples as to what you mean by this?

[QUOTE=Dylan14;532135]As for the time stamp: the script only counts lines that have those strings that I mentioned. Since the time stamp looks something like this:

[CODE][Thu Dec 5 17:56:55 2019][/CODE]the script ignores it since those strings do not appear.[/QUOTE]That's what I said. You did the right thing, matching to count a line (not matching to exclude a line, which leads to needing to identify all cases of lines to exclude).
[QUOTE]As for manual edits: would you mind providing some examples as to what you mean by this?[/QUOTE]Someone manually edits the results file and puts in a text comment or just an extra line break. These are very common here. Also somewhat already handled by your approach, and also not an issue here since I'm using other means to submit results. You could have trouble if someone adds a comment that happens to fit your "no factor" or "found" string matches. "#retest for whether no factor found" would be an unfortunate choice of comment.

Introducing tf1G.py v0.10:

Now the count_exponents_tested function will look at each line and see if the line starts with # or ; (# denotes a comment line in most things, ; is used in mprime/Prime95). If it does, the program will move on to the next line (thanks kriesel for the feedback!).

[QUOTE=kracker;532099]Just got a one question survey while running colab saying "Would you be interested in a paid, premium version of colab?""[/QUOTE]

I haven't seen that survey but my answer would be YES if I could have a premium GPU 24 hours per day.

[QUOTE=Chuck;532145]I haven't seen that survey but my answer would be YES if I could have a premium GPU 24 hours per day.[/QUOTE]

+1! I'd have to compare it to the costs of GCE, EC2 etc, but I would be very interested in knowing the terms of the offer.

T4 and P4 seem to be two different fish. They may be two different chips, or one chip with different chops. Like two copies of the same hand which once had the index finger amputated, and once had the middle finger amputated, it seems that T4 is about 4 times as fast as a K80 for TF, and only quarter speed at LL, while P4 is about 1.5 times TF and 1/2 times LL compared with k80. The P100 seems to be another fish too, being about 2.5xTF and 2xLL. YMMV...

[QUOTE=LaurV;532149]T4 and P4 seem to be two different fish. They may be two different chips, or one chip with different chops. Like two copies of the same hand which once had the index finger amputated, and once had the middle finger amputated, it seems that T4 is about 4 times as fast as a K80 for TF, and only quarter speed at LL, while P4 is about 1.5 times TF and 1/2 times LL compared with k80. The P100 seems to be another fish too, being about 2.5xTF and 2xLL. YMMV...[/QUOTE]

Some specs on all the GPU's we've gotten... no idea if it's 100% accurate.

[URL="https://www.techpowerup.com/gpu-specs/tesla-k80.c2616"]NVIDIA Tesla K80
[/URL][URL="https://www.techpowerup.com/gpu-specs/tesla-p4.c2879"]NVIDIA Tesla P4
[/URL][URL="https://www.techpowerup.com/gpu-specs/tesla-t4.c3316"]NVIDIA Tesla T4[/URL]
[URL="https://www.techpowerup.com/gpu-specs/tesla-p100-pcie-16-gb.c2888"]NVIDIA Tesla P100[/URL]

[url]https://en.wikipedia.org/wiki/List_of_Nvidia_graphics_processing_units#Tesla[/url]

P4 is Pascal (10xx), T4 is Turing (RTX 20xx, GTX 16xx). Neither is good at DP. T4 >> P4 at TF.

I notice we've gotten to try every one of [URL="https://cloud.google.com/gpu/"]Google Cloud's GPU's[/URL], [I]except [/I]the V100...
:whistle: