[QUOTE=storm5510;530063]If Google had written, "Failed to assign a backend" as "No GPU available," it would have been far better. I would have simply stopped and waited several hours instead of trying to figure out what was wrong on my end.[/QUOTE]
If you follow the link in the pop-up it tells you what the deal is. GPU's are available to those who are using them interactively.

[QUOTE=Uncwilly;530065]If you follow the link in the pop-up it tells you what the deal is. GPU's are available to those who are using them interactively.[/QUOTE]

I have probably seen this but did not pay any attention to it. Live and learn. :smile:

I was looking at my manual assignments on [I]GPU72[/I] a short time ago. I found four which were two days old. They apparently never made it into [I]mfaktc's[/I] worktodo file. This happens occasionally. I manually added them.

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, e.g:[quote][COLOR="Red"]UID: JamesHeinrich/ColabA, [/COLOR]no factor for M99330661 from 2^74 to 2^75 [mfaktc 0.21 barrett76_mul32_gs][/quote]I assume GPU72 knows our PrimeNet username somewhere, if not that may need to be configurable from somewhere.

[QUOTE=James Heinrich;530147]I assume GPU72 knows our PrimeNet username somewhere, if not that may need to be configurable from somewhere.[/QUOTE]

Good idea! Thanks.

GPU72 doesn't currently know /everyone's/ PNUN -- only those currently using the Proxy.

Being able to set this by way of the Web UI is mapped for the near future. This will actually be required for the automatic submission of Notebook results.

Importantly, GPU72 does not currently, nor will it ever need to, know the worker's PN PW.

Quick update: rsyncing of all the data from the old server to the new is almost complete. The next step will be to first have the old server use the MariaDB on the new server, and then I'll update the DNS records (which can take up to 24 hours to propagate fully).

Currently programmed for tomorrow around 1400 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, e.g:I assume GPU72 knows our PrimeNet username somewhere, if not that may need to be configurable from somewhere.[/QUOTE]

I have used this in [I]mfaktc[/I] before. It seem that, if [I]PrimeNet[/I] didn't assign it, then it ignores the user info. This, and the lack of an assignment ID.

[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, e.g:I assume GPU72 knows our PrimeNet username somewhere, if not that may need to be configurable from somewhere.[/QUOTE]
This is configurable in mfaktX ini file.
By the way, James, any issue with the "income" in the last two days for you site? :razz:

[QUOTE=LaurV;530166]This is configurable in mfaktX ini file.[/QUOTE]For standalone use, of course. But I'm talking about the lines from Colaboratory as reported here:
[url]https://www.gpu72.com/account/instances/results/[/url]

[QUOTE=LaurV;530166]By the way, James, any issue with the "income" in the last two days for you site? :razz:[/QUOTE]Income? Not sure what you mean?

The lines for colab are reported by mfaktc that Chris' script uploads into colab. That file he can change and upload the proper one, or you can edit by yourself in the colab folder and add the user/computer lines.

And by "income" I mean me going through your 3G exponents to 69-70 bitlevel, 120 thousand exponents per day for the last two days.

The "connection" between the two things, is that somewhere in the middle of that process I realized (reading more through your site) that I could also get credit for the about 3000 factors, and just added the user/computer to the factor lines, as described above. But you can see from the IP address that it was me before, too.

[QUOTE=LaurV;530171]or you can edit by yourself in the colab folder and add the user/computer lines.[/quote]I would if I knew how/where to do that, but I don't. Can you point me in the right direction?

[QUOTE=LaurV;530171]And by "income" I mean me going through your 3G exponents to 69-70 bitlevel, 120 thousand exponents per day for the last two days.
But you can see from the IP address that it was me before, too.[/quote]No, I hadn't noticed a particular spike. That would be about 5000GHd/d, or roughly 20% of the project throughput, but the numbers vary a fair bit from day to day (due to relatively low number of participants therefore less average smoothing effect). I do see a minor spike on 08-Nov, but nothing like the massive 250000+ spikes from [i]ramgeis[/i] has been known to contribute once a month or so (he missed October, but overall throughput is up so maybe he's reporting results daily instead of monthly now). But any contributions are welcome. We're on the verge of having everything below 4G cleared to 2[sup]68[/sup]. :smile:

BTW: if you missed getting credit for factors, just email me a list of the factors and your user/comp name and I'll make sure the credit gets attached, it's simple enough.

[QUOTE=James Heinrich;530173]
BTW: if you missed getting credit for factors, just email me a list of the factors and your user/comp name and I'll make sure the credit gets attached, it's simple enough.[/QUOTE]
I have no idea if I missed any credit, because I don't know where to look for. In fact, as explained above, I had no idea that the work is credited in any way, before reading in your page, the night before last night, when I changed the ini files to report the user/computer too. Some work was done before that also, from the same computer, and moving about 280000 exponents from 68 to 69/70/72 bits can be clearly seen in the visualization tool.

Related of how to change the ini files for colab, you can click on "files" and then click the "up dir" (the dot-dot entry) then you can find the files in the home folder. Asuming you run your own copy (and didn't directly launch the one from Chris' folder) then you can edit the ini file
[ATTACH]21282[/ATTACH]. [ATTACH]21283[/ATTACH]

However, according with my (long ago) knowledge, Primenet won't cope well with lines having userid/computer in front. This knowledge of mine may be outdated... We don't use user/comp when we report with MISFIT.
Edit: when you edit the file, you don't necessarily need to change the user name. I won't feel sorry If I receive some credit for the work done by yourself. That is why I let it in clear :razz: