Colab CPUs
 

I didn't realize I needed to relaunch the notebooks so I have just done that. In my "view assignments" list on GPU72 I see the P-1 assignments, but where do I go to see their progress?

[QUOTE=petrw1;538540]I'm interested. I'd like to do DC-P1 work.[/QUOTE]

Yeah... That's been envisioned.

Because of the race into the 10xMs by the Cat 3 and 4s, there are a lot of candidates which get LL'ed without a P-1. I'm currently targeting this myself (there are 317 such candidates needing a DC P-1).

I also figured you (and perhaps a few others) would be interested in strategically redoing poorly P-1'ed candidates... :wink:

[QUOTE=petrw1;538540]Will it allow me to provide my own worktodo lines?[/QUOTE]

Nope... These must be issued by GPU72 to be managed by all the ephemeral instance runs. But I'm open to suggestions as to ranges of interest.

[QUOTE=Chuck;538541]...but where do I go to see their progress?[/QUOTE]

They /should/ be updated on your Assignments page. The checkpoints are uploaded every ten minutes, and the percentage completed value every hour.

OH, SHOOT!!!

There might be a problem with the checkpoint uploading!!! I developed this using my Reverse tunnels, and it appears the cron sub-system this relies on isn't being brought up correctly by the CPU Payload. Please standby. (Note, this doesn't effect the GPU work in any way, this is still sane.)

[QUOTE=chalsall;538543]They /should/ be updated on your Assignments page. The checkpoints are uploaded every ten minutes, and the percentage completed value every hour.[/QUOTE]

OK I probably just need to wait.

[QUOTE=Chuck;538544]OK I probably just need to wait.[/QUOTE]

OK... Fixed the CRON based uploader issue.

Chuck... Could you please stop and restart your Notebooks? You'll be issued new P-1 assignments, but they should have the checkpoints being uploaded properly, and the Updated field change every ten minutes.

Sorry about that. An example of development rigging having an impact on the deployed code. A bit like quantum observer disruption of a system, only different... :wink:

[QUOTE=chalsall;538547]OK... Fixed the CRON based uploader issue.

Chuck... Could you please stop and restart your Notebooks? You'll be issued new P-1 assignments, but they should have the checkpoints being uploaded properly, and the Updated field change every ten minutes.

Sorry about that. An example of development rigging having an impact on the deployed code. A bit like quantum observer disruption of a system, only different... :wink:[/QUOTE]

Done.

[QUOTE=Chuck;538556]Done.[/QUOTE]

Excellent! Thanks. And I see your checkpoints! :tu:

Thumbs Up
 

Appears I have Colab running 2 instances of TF AND P1

[QUOTE=petrw1;538658]Appears I have Colab running 2 instances of TF AND P1[/QUOTE]

Still seeing the sessions die after an hour or two.

If the session dies that is running both GPU-TF and CPU-P1 … and I restart it is it safe to assume that both the TF and P1 will be picked up again after the restart?

Any idea if the session would live longer if I ran ONLY P1.
That seems to be more in need anyway.

What is the quick way to add that snippet of code into the notebook please?

I did find another way, and it is working on a P1, but think there must be a simpler way :)

[QUOTE=bayanne;538687]What is the quick way to add that snippet of code into the notebook please?[/QUOTE]I don't know how you're [i]supposed[/i] to do it, but from the [B]⋮[/B] menu hovering in the upper right, choose Form->Show Code and then you get a sliver of code box on the left in which to find (~line 20) and edit the !wget line.