FoldingFodder wrote:...Doing so shouldn't cause any issues if FAH is programmed correctly. In my own work, if there is anything that will cause fatal errors, i inhibit the user from making the change or i don't allow the change to go live until it's safe to do so. I'm assuming that the FAH software is developed at Standford (?) and if so, i'm going to assume they've already thought of someone making a change part way through processing a work unit...
The reason it might cause issues is because of the underlying tools that F@H uses which is GROMACS (for CPU). GROMACS are used by scientists for molecular simulations and once it is started with X CPUs, everything is set-up for X. Changing it to Y mid run does not guarantee that it will continue thus can fail. The integrity of science can't be compromised.
The F@H Software isn't developed at Stanford, it is developed by Joseph Coffland (a third party) and he's a single person who looks after most of the F@H code base (clients for Windows, Linux, macOS, F@H Server configurations, etc.).
FoldingFodder wrote:...
Here is the log. The log started once i did the command
FAHclient --verbosity 5. I terminated the process at the end with ctrl + c...
Can you please use the default value of 3 since 5 prints out everything and I don't know what settings have been changed and isn't helpful for troubleshooting.
Most of the files look normal except these two which I don't recognize:
<removed>\Documents\Programming\Clone command.txt
<removed>\Documents\Programming\clone.txt
It's weird that the GUI shows 2 CPUs but the instructions for the FahCore_a7 shows 6:
<removed>03:27:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" <removed>\Documents\Programming\cores/cores.foldingathome.org/v7/win/64bit/avx/Core_a7.fah/FahCore_a7.exe -dir 00 -suffix 01 -version 705 -lifeline 20052 -checkpoint 15 -np 6
Something is not right since you have a single CPU Slot which means a single instance of FahCore_a7. You have two instances of FahCore_a7 running on your system.
FoldingFodder wrote:...The work unit had been running for just over 4 hours at that point...
The problem is that you have 2 instances of FahCore_a7 and I am not sure why that is. It seems to be competing with the CPU resources.
FoldingFodder wrote:...The log shows a CPU slot utilizing 6 threads and a GPU slot. As you can see it's downloaded a new work unit and started working on it...
Please note that the GPU you have isn't supported by F@H. You need to have OpenCL 1.2 and Double Precision and your GeForce GT 630M only supports OpenCL 1.1:
https://www.techpowerup.com/gpu-specs/g ... -630m.c353
FoldingFodder wrote:...Are you the dev by chance?
Nope, I am not affiliated with the official F@H Team in any manner, just a volunteer that works with them

There is only a single Developer for F@H (memberlist.php?mode=viewprofile&u=5075).
My suggestions are:
1) Reset the verbosity level to 3
2) Remove your GPU Slot
3) Set the CPU Slot to finish
4) Once your CPU Slot is free, check you have 6 CPUs assigned to it via FAHControl -> Configure -> Sots Tab -> CPU Slot -> Edit -> CPU value is 6 and it confirm that the config.xml file has this:
15:12:48: <slot id='0' type='CPU'>
15:12:48: <cpus v='6'/>
15:12:48: </slot>
5) Start CPU Slot and verify that a single instance of FahCore_a7 is running via Task Manager