[QUOTE=James Heinrich;530216]I found 39 factors without user identification between 3321M-3738M from your IP (plus another 975 with UID). I have added your name to those factors. There is (currently) no way for you to get a list of factors you've found.[/QUOTE]
Well, then my suspicion is that something is wrong there. There should have been about three times that amount. Are you sure that you are recording all the submissions? A negative answer should also justify why there is no "spike" in the graph. In the first days there was nobody else moving numbers in that range, and there should be about 3000 factors. I was not sure, therefore after our former discussion, I started logging/recording the factors. Since my last post, I have about 5600 factors and moved about 400k exponents (i.e. about 200k, two bitlevels) with the same hardware and setup as before. Do your records match? (the "no factor" I reported, but didn't keep the record; should I? The table seems that didn't move, but I assume you rebuild it once or twice per day, and that is when I sleep, i.e. in few minutes... 1:00 AM here...)

[QUOTE=LaurV;530308]Since my last post, I have about 5600 factors...
I assume you rebuild it once or twice per day, and that is when I sleep[/QUOTE]The number of factors seems approximately right, checking for new factors in 3320M-3739M since 2019-11-10 00:00:00 I get:[code]mysql> SELECT "371x" AS `mrange`, COUNT(*) AS `howmany`, DATE(`timestamp_found`) AS `date` FROM `known_factors_371` WHERE (`timestamp_found` > "2019-11-10") GROUP BY `date` ASC;
+--------+---------+------------+
| mrange | howmany | date |
+--------+---------+------------+
| 371x | 432 | 2019-11-11 |
| 372x | 1251 | 2019-11-10 |
| 372x | 2318 | 2019-11-11 |
| 373x | 1845 | 2019-11-10 |
+--------+---------+------------+[/code]The chart numbers are updated as the results come in, but it takes some time to work through the large number of results so you won't see the chart numbers change immediately; the charts are also rebuilt every night approx 2am UTC.

[QUOTE=James Heinrich;530147]For the [url=https://www.gpu72.com/account/instances/results/]result lines[/url] that we're currently copy-pasting to manual_results, is it possible to prepend the user/computer identifier string, using the configured InstanceName...[/QUOTE]

Hey. OK, finally had the ninety seconds it took to apply this delta.

I copy-and-pasted the results from my own workers into Primenet's manual submission page, and the results were accepted. However, I don't see any indication on any of the views I can access of this knowledge being captured.

[CODE]UID: MYPNUN/A3_SS, no factor for M99338087 from 2^76 to 2^77 [mfaktc 0.21 barrett87_mul32_gs]
UID: MYPNUN/A3_BU_1, no factor for M99900599 from 2^76 to 2^77 [mfaktc 0.21 barrett87_mul32_gs]
[/CODE]

[QUOTE=chalsall;530483]Hey. OK, finally had the ninety seconds it took to apply this delta.
However, I don't see any indication on any of the views I can access of this knowledge being captured.[/QUOTE]It is being captured, the raw submission text is captured, and is used as the basis for generating the "pretty" public-facing values.
Thanks for adding that.

I'm having more and more times where my Colab instance times out quickly, or I can't connect to a GPU instance, and generally I'm not having much luck getting sustained throughput (but any throughput is more than I would otherwise be able to contribute, so can't really complain).

But I ran into something new today (on both instances):[code]Beginning GPU Trial Factoring Environment Bootstrapping...
Please see https://www.gpu72.com/ for additional details.

20191119_150834: GPU72 TF V0.32 Bootstrap starting...
20191119_150834: Working as "10bcb2acdbb748af637902b48f4240e3"...

20191119_150834: Installing needed packages (1/3)
20191119_150843: Installing needed packages (2/3)
20191119_150853: Installing needed packages (3/3)
20191119_150925: Fetching initial work...
20191119_150926: Bootstrap finished. Exiting.[/code]

I reported the same on the colab thread.
Chris said they made a change on their end and mfaktc is no longer working.

[QUOTE=James Heinrich;530991]I'm having more and more times where my Colab instance times out quickly, or I can't connect to a GPU instance, and generally I'm not having much luck getting sustained throughput (but any throughput is more than I would otherwise be able to contribute, so can't really complain).

But I ran into something new today (on both instances):[code]Beginning GPU Trial Factoring Environment Bootstrapping...
Please see https://www.gpu72.com/ for additional details.

20191119_150834: GPU72 TF V0.32 Bootstrap starting...
20191119_150834: Working as "10bcb2acdbb748af637902b48f4240e3"...

20191119_150834: Installing needed packages (1/3)
20191119_150843: Installing needed packages (2/3)
20191119_150853: Installing needed packages (3/3)
20191119_150925: Fetching initial work...
20191119_150926: Bootstrap finished. Exiting.[/code][/QUOTE]

[QUOTE=James Heinrich;530991]I'm having more and more times where my Colab instance times out quickly, or I can't connect to a GPU instance, and generally I'm not having much luck getting sustained throughput (but any throughput is more than I would otherwise be able to contribute, so can't really complain).[/QUOTE]

[QUOTE=petrw1;530993]I reported the same on the colab thread.
Chris said they made a change on their end and mfaktc is no longer working.[/QUOTE]

Please see this post for a workaround. [url]https://www.mersenneforum.org/showpost.php?p=530962&postcount=571[/url]

[QUOTE=James Heinrich;530991]
20191119_150834: GPU72 TF V0.32 Bootstrap starting...
20191119_150834: Working as [SPOILER]0bcb2acdbb748af637902b48f4240e3[/SPOILER]...
20191119_150834: Installing needed packages (1/3)
20191119_150843: Installing needed packages (2/3)
20191119_150853: Installing needed packages (3/3)
20191119_150925: Fetching initial work...
20191119_150926: Bootstrap finished. Exiting.[/QUOTE]

I received the same a few hours ago.

My typical instance run time is around nine hours. I have two notebooks which I alternate between. Perhaps leaving each rest a day helps my run time...

But the fix that Uncwilly posted does work:[list=1][*]click "+ Code", copy-paste that line into the new box that appears:
[code]!apt-get install cuda-cudart-10-0[/code][*]click (►) to run the code, it takes about 10 seconds (and doesn't show a clear "done", just note when the circle stops spinning). [*]click the (►) on the main section and it will run as it did before.[/list]

Also, no need to open any +code, every time you run something, there is a small rectangle appearing in your terminal window, that rectangle is an input box where you can write any OS commands.

[QUOTE=James Heinrich;531040]But the fix that Uncwilly posted does work:[LIST=1][*]click "+ Code", copy-paste that line into the new box that appears:
[code]!apt-get install cuda-cudart-10-0[/code][*]click (►) to run the code, it takes about 10 seconds (and doesn't show a clear "done", just note when the circle stops spinning).[*]click the (►) on the main section and it will run as it did before.[/LIST][/QUOTE]

It works well. I take it that this is a [U]temporary[/U] fix?