[QUOTE=chalsall;529181]I had hoped to get it finished yesterday, but you will soon be able to change the WorkType for each AKEY.[/QUOTE]

OK, this has now been enabled. Go to your [URL="https://www.gpu72.com/account/instances/"]Account's Notebook Access Keys[/URL] list. Under the "GPU Work Type" column, each field is "clickable" to take you to the new "Edit Notebook Access Key".

Here you can change the name if the AKey (if you ever had a need to), as well as the associated Work Type.

The options are "Let GPU72 Decide", "LL TF (Breadth First)", "LL TF (Depth First)", "DC TF (Breadth First)", "DC TF (Depth First)", and "DC Already Done TF'ing".

Please note that the changed work type names are "unsurprising", in that if previously you had set "LL TF" that now means "LL TF (Breadth First)". Just so everyone knows before choosing Depth, a single 76 -> 77-bit run takes something like nine hours on a K80.

You will also notice a new column to the list: "CPU Work Type". You'll probably easily guess what that's for... :smile:

Feedback / SPEs / etc welcomed.

I spotted a couple errors related to the DC-TF stats handling.
One I post about here: [url]https://mersenneforum.org/showthread.php?t=24881[/url]

The other is that I can see my DC rank in my Individual Overall Statistics. But, when I go to look up my ranking at [url]https://www.gpu72.com/reports/workers/dctf/[/url] I am not there at all. I have been there. This has happened before the other day and corrected itself somehow. Attached images show the issue.

[QUOTE=chalsall;529242]OK, this has now been enabled. Go to your [URL="https://www.gpu72.com/account/instances/"]Account's Notebook Access Keys[/URL] list. Under the "GPU Work Type" column, each field is "clickable" to take you to the new "Edit Notebook Access Key"...[/QUOTE]

[COLOR=Sienna]I am getting a security warning when I try to go to gpu72.com. Something about a security certificate, I believe. This may be nothing. However, I thought I'd pass it on, This would be with Mozilla Firefox and Windows 10 Pro v1903.x64. [/COLOR]

Same here, with Win 10 / Google Chrome. I think it´s back to normal, tho.

[QUOTE=storm5510;529263][COLOR=Sienna]I am getting a security warning when I try to go to gpu72.com. Something about a security certificate, I believe.[/COLOR][/QUOTE]

Yup. Stupid SysAdmin error on my end -- with everything going on, I missed the notice that the Cert was about to expire... Fixed.

[QUOTE=storm5510;529263][COLOR=Sienna]I am getting a security warning when I try to go to gpu72.com. Something about a security certificate, I believe. This may be nothing. However, I thought I'd pass it on, This would be with Mozilla Firefox and Windows 10 Pro v1903.x64. [/COLOR][/QUOTE]
Firefox does that to me frequently. I may have been bopping around a site for several hops before it suddenly decides that I am in deadly danger and refuses to continue.


On the other current topic, I got my most recent TF assignments in the LL range with What Makes Sense. I received some in the 94036xxx area and some in 94001xxx. FWIW, I'll use LG72D in the future.

[QUOTE=chalsall;529265]Yup. Stupid SysAdmin error on my end -- with everything going on, I missed the notice that the Cert was about to expire... Fixed.[/QUOTE]

No, not stupid, just busy. :smile:

Both [I]Windows 10[/I] and [I]Firefox[/I] had recently updated, so I thought it may be a problem on my end. I go there (gpu72.com) from time-to-time to see what is going on, but not recently. I don't need to with the auto-fetch.

[QUOTE=kladner]On the other current topic, I got my most recent TF assignments in the LL range with What Makes Sense. I received some in the 94036xxx area and some in 94001xxx. FWIW, I'll use LG72D in the future. [/QUOTE]

My assignments in the past week have all been in the 95xxxxxx area. Just a few days ago, it was 950xxxxx.. Today, it is 953xxxxx. So, that area is progressing rapidly at the current bit assignments. 2[SUP]73[/SUP] to 2[SUP]74[/SUP]. I also use the "What Makes Sense" setting. Some of the RTX guys have been busy. The P-1's I experimented with had all been factored to 2[SUP]77[/SUP].

[QUOTE=storm5510;529280]My assignments in the past week have all been in the 95xxxxxx area. Just a few days ago, it was 950xxxxx.. Today, it is 953xxxxx. So, that area is progressing rapidly at the current bit assignments...[/QUOTE]

Yup. A manageable race condition...

Just because it might be of some interest to some of you, attached is one of the Admin graphs I use for situational awareness. It's kinda cool watching the bars change colors over the days and weeks... :smile:

[QUOTE=chalsall;529291]Yup. A manageable race condition...

Just because it might be of some interest to some of you, attached is one of the Admin graphs I use for situational awareness. It's kinda cool watching the bars change colors over the days and weeks... :smile:[/QUOTE]

I had to study your bar graph for a few minutes. Very interesting.

Now, my assignments are at 956xxxxx so it is moving right along. Of course, others will have to come in behind to run the bit levels higher. Do you have a ceiling value for this work?

[QUOTE=storm5510;529318]Of course, others will have to come in behind to run the bit levels higher. Do you have a ceiling value for this work?[/QUOTE]

Yup, that's how this thing works... :smile:

Not clear what you mean by ceiling value. We "release" back to Primenet at 77 (currently).

I should have mentioned that the assignments above were made without a bit level specified. They came in at 76 to 77.