Folding Forum

We recently moved from fahclient V7.6 to fah-client V8.3.

Once fah-client was up and running I had to dump the first few WUs as our eta exceeded the WU deadline.
We were able to complete a few WUs since but now we are constantly getting WU that can not be completed in time.
For instance we keep getting project 192?? By Tanner Dean, University of Illinois, Target: unspecified.

We tried to change our Cause from Any to a specific cause in the hope that we will download manageable WUs.
But even though we changed the Cause category and restart the fah-client service (and also rebooted the laptop) we still get WUs from project 192?? By Tanner Dean, University of Illinois, Target: unspecified.

We would really would like to contribute to folding@home with our old laptop instead of creating more e-waste.

Is there a way to get our old laptop folding within a WU deadline. The laptop runs 24/7 and is solely dedicated to fah-cleint.

I've had the same problem with a couple of recent WUs:

• Time now + ETA > Timeout

I assume that the correct response is to dump the WU as soon as possible, and hope that the next one can be completed within the deadline.

Edit: I started with FAH a couple of weeks ago, and have completed 45 WUs with few problems until now.

I have a suggestion for the WU Details window:

In addition to the Assign Time, Deadline, and Timeout fields, show Time now + ETA . That makes it easy for the user to see if Time now + ETA > Timeout.

Even more user friendly: add a flag beside the Account settings icon that appears/changes colour if Time now + ETA > Timeout.

malkie wrote: ↑Tue Aug 20, 2024 2:56 amI assume that the correct response is to dump the WU as soon as possible, and hope that the next one can be completed within the deadline.

Yes, this is what we have been doing as well. Which brings up the question; what is the difference between Pause+Dump and Finish?

DoctorBob wrote: ↑Tue Aug 20, 2024 5:21 am

malkie wrote: ↑Tue Aug 20, 2024 2:56 amI assume that the correct response is to dump the WU as soon as possible, and hope that the next one can be completed within the deadline.

Yes, this is what we have been doing as well. Which brings up the question; what is the difference between Pause+Dump and Finish?

Since the issue is not having time to complete the WU, I always Pause then dump. Finish up then Pause would still run into the same problem of not being able to complete the WU.

This should be fixed again. The researchers are looking into why the setting keeps reverting to allow these assignments, they did not explicitly change them.

Joe_H wrote: ↑Tue Aug 20, 2024 3:29 pm This should be fixed again. The researchers are looking into why the setting keeps reverting to allow these assignments, they did not explicitly change them.

What do you think about the idea of providing more "donor friendly" info on the WU page?

Perhaps also including an option for the conversion of times to the donor's local time zone as well?

ETA: Duhhh - somehow I failed to notice that the times are in my local time zone! How/why do people (or at least one person) not see that?

I didn't find any useful informations (project number and number of CPU cores) in this thread to forward the issue to the researchers ...

Next time it happens, post a report in the appropriate section of the forum with enough informations, like this one : viewtopic.php?t=41812

toTOW wrote: ↑Wed Aug 21, 2024 11:02 pm I didn't find any useful informations (project number and number of CPU cores) in this thread to forward the issue to the researchers ...

Next time it happens, post a report in the appropriate section of the forum with enough informations, like this one : viewtopic.php?t=41812

I don't know what you mean by "in the appropriate section of the forum", so I'm posting here
Below are the log and a couple of screenshots from my current WU.

Machine overview:

WU details:

Machine details:

Machine settings:

====================

As you can see,

Assign Time: 2024-08-22T 21:23:39Z
+
ETA: 2 16:00:00
>
Timeout: 2024-08-24T 09:23:39Z

I'm going to dump this WU, and hope that the next one is within my machine's capacity as set up for F@H.

BTW - my apologies - I don't know where my head was before, but I see that the times in the WU details screen are in local time

============================================

21:32:41:I1:WU77:Received WU P18488 R0 C97 G33
21:32:42:I3:WU77:Running FahCore: C:\ProgramData\FAHClient\cores/openmm-core-22/fahcore-22-windows-64bit-release-0.0.20/FahCore_22.exe -dir p7d84xvIx11z03SqG5ZOPQ4njBBy2Zm3Qk8ecOJhXEk -suffix 01 -version 8.3.18 -lifeline 21608 -gpu-vendor amd -opencl-platform 0 -opencl-device 1 -gpu 1
21:32:42:I3:WU77:Started FahCore on PID 3148
21:32:42:I1:WU77:*********************** Log Started 2024-08-22T21:32:42Z ***********************
21:32:42:I1:WU77:*************************** Core22 Folding@home Core ***************************
21:32:42:I1:WU77: Core: Core22
21:32:42:I1:WU77: Type: 0x22
21:32:42:I1:WU77: Version: 0.0.20
21:32:42:I1:WU77: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
21:32:42:I1:WU77: Copyright: 2020 foldingathome.org
21:32:42:I1:WU77: Homepage: https://foldingathome.org/
21:32:42:I1:WU77: Date: Jan 20 2022
21:32:42:I1:WU77: Time: 01:15:36
21:32:42:I1:WU77: Revision: 3f211b8a4346514edbff34e3cb1c0e0ec951373c
21:32:42:I1:WU77: Branch: HEAD
21:32:42:I1:WU77: Compiler: Visual C++
21:32:42:I1:WU77: Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
21:32:42:I1:WU77: -DOPENMM_VERSION="\"7.7.0\""
21:32:42:I1:WU77: Platform: win32 10
21:32:42:I1:WU77: Bits: 64
21:32:42:I1:WU77: Mode: Release
21:32:42:I1:WU77:Maintainers: John Chodera <john.chodera@choderalab.org> and Peter Eastman
21:32:42:I1:WU77: <peastman@stanford.edu>
21:32:42:I1:WU77: Args: -dir p7d84xvIx11z03SqG5ZOPQ4njBBy2Zm3Qk8ecOJhXEk -suffix 01
21:32:42:I1:WU77: -version 8.3.18 -lifeline 21608 -gpu-vendor amd -opencl-platform 0
21:32:42:I1:WU77: -opencl-device 1 -gpu 1
21:32:42:I1:WU77:************************************ libFAH ************************************
21:32:42:I1:WU77: Date: Jan 20 2022
21:32:42:I1:WU77: Time: 01:14:17
21:32:42:I1:WU77: Revision: 9f4ad694e75c2350d4bb6b8b5b769ba27e483a2f
21:32:42:I1:WU77: Branch: HEAD
21:32:42:I1:WU77: Compiler: Visual C++
21:32:42:I1:WU77: Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
21:32:42:I1:WU77: Platform: win32 10
21:32:42:I1:WU77: Bits: 64
21:32:42:I1:WU77: Mode: Release
21:32:42:I1:WU77:************************************ CBang *************************************
21:32:42:I1:WU77: Date: Jan 20 2022
21:32:42:I1:WU77: Time: 01:13:20
21:32:42:I1:WU77: Revision: ab023d155b446906d55b0f6c9a1eedeea04f7a1a
21:32:42:I1:WU77: Branch: HEAD
21:32:42:I1:WU77: Compiler: Visual C++
21:32:42:I1:WU77: Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
21:32:42:I1:WU77: Platform: win32 10
21:32:42:I1:WU77: Bits: 64
21:32:42:I1:WU77: Mode: Release
21:32:42:I1:WU77:************************************ System ************************************
21:32:42:I1:WU77: CPU: AMD Ryzen 5 3400G with Radeon Vega Graphics
21:32:42:I1:WU77: CPU ID: AuthenticAMD Family 23 Model 24 Stepping 1
21:32:42:I1:WU77: CPUs: 8
21:32:42:I1:WU77: Memory: 13.93GiB
21:32:42:I1:WU77:Free Memory: 5.61GiB
21:32:42:I1:WU77: Threads: WINDOWS_THREADS
21:32:42:I1:WU77: OS Version: 6.2
21:32:42:I1:WU77:Has Battery: false
21:32:42:I1:WU77: On Battery: false
21:32:42:I1:WU77: UTC Offset: -4
21:32:42:I1:WU77: PID: 3148
21:32:42:I1:WU77: CWD: C:\ProgramData\FAHClient\work
21:32:42:I1:WU77:************************************ OpenMM ************************************
21:32:42:I1:WU77: Version: 7.7.0
21:32:42:I1:WU77:********************************************************************************
21:32:42:I1:WU77:Project: 18488 (Run 0, Clone 97, Gen 33)
21:32:42:I1:WU77:Reading tar file core.xml
21:32:42:I1:WU77:Reading tar file integrator.xml
21:32:42:I1:WU77:Reading tar file state.xml
21:32:43:I1:WU77:Reading tar file system.xml
21:32:43:I1:WU77:Digital signatures verified
21:32:43:I1:WU77:Folding@home GPU Core22 Folding@home Core
21:32:43:I1:WU77:Version 0.0.20
21:32:43:I1:WU77: Checkpoint write interval: 100000 steps (2%) [50 total]
21:32:43:I1:WU77: JSON viewer frame write interval: 50000 steps (1%) [100 total]
21:32:43:I1:WU77: XTC frame write interval: 500000 steps (10%) [10 total]
21:32:43:I1:WU77: Global context and integrator variables write interval: disabled
21:32:43:I1:WU77:There are 3 platforms available.
21:32:43:I1:WU77:Platform 0: Reference
21:32:43:I1:WU77:Platform 1: CPU
21:32:43:I1:WU77:Platform 2: OpenCL
21:32:43:I1:WU77: opencl-device 1 specified
21:32:58:I1:WU77:Attempting to create OpenCL context:
21:32:58:I1:WU77: Configuring platform OpenCL
21:33:05:I1:WU77: Using OpenCL on platformId 0 and gpu 1
21:33:05:I1:WU77:Completed 0 out of 5000000 steps (0%)
21:33:05:I1:WU77:Checkpoint completed at step 0
22:13:52:I1:WU77:Completed 50000 out of 5000000 steps (1%)
22:56:45:I1:WU77:Completed 100000 out of 5000000 steps (2%)
22:56:46:I1:WU77:Checkpoint completed at step 100000
23:37:15:I1:WU77:Completed 150000 out of 5000000 steps (3%)
00:20:05:I1:WU77:Completed 200000 out of 5000000 steps (4%)
00:20:06:I1:WU77:Checkpoint completed at step 200000
01:00:36:I1:WU77:Completed 250000 out of 5000000 steps (5%)
01:40:59:I1:WU77:Completed 300000 out of 5000000 steps (6%)
01:41:00:I1:WU77:Checkpoint completed at step 300000

Guys, if you are receiving projects which are not fit for your GPUs, provide full system details (like screenshots provided by malkie), or just simply:
Thanks

As for p18488, not sure what happened there, but it will be fixed soon, and you won't receive any of them in the future

Perhaps also including an option for the conversion of times to the donor's local time zone as well?

We are seeing the same issue here in our timezone. Brisbane, Qld. Australia (UTC+10).

We completed the last WU around 9:00am (28/08/2024)
The new WU started at 10:22pm (2024/08/27). Somewhere in North America?




Is there a way to change the timezone to local time? Or at least know what the "Assign Time" timezone is.

All times the client uses are +00:00
Z is Zulu

calxalot wrote: ↑Wed Aug 28, 2024 12:22 am All times the client uses are +00:00
Z is Zulu

Thank you for this information. Easy to convert to local time.