Question about new cores when they become available

[mwroggenbuck]

When a new version of a core becomes available, is the client smart enough to download and replace the old core? Or does something manual have to happen?

Just curious.

[JimboPalmer]

In general, the first Work unit written for the new Core causes it to be downloaded automatically.

In practice, that routine is used so rarely, it is not always perfect.

[PantherX]

There are two answers to your question, depending on the interpretation of "new cores".

New version of FahCore_X -> In virtually 100% of the time, a new version would be automatically supported by the existing client. The Project has a minimum version of FahCore_X version Y and it is also backwards compatible to ensure that if a WU from a different Project is downloaded, it can still fold. Keep in mind that it is minimum version, not the maximum version.

New FahCore_Z -> In most cases, it tends to work fine. However, there are exceptions to when a new version of the client was required simply because the client needed to detect additional information of the system in order for the new FahCore_Z to be downloaded and handled by the client. Also, the researchers do test that the new FahCore_Z can operate with the latest version of the client and ensure to provide sufficient communications to ensure that most donors who are actively participating, can update without issues.

[mwroggenbuck]

Now I am more confused.

Let's say that FahCore_22 goes from Version 0.0.5 to version 0.0.6. I currently have 0.0.5 on my system. Will version 0.0.6 replace it automatically?

[HaloJones]

Now I am more confused.

Let's say that FahCore_22 goes from Version 0.0.5 to version 0.0.6. I currently have 0.0.5 on my system. Will version 0.0.6 replace it automatically?

depends.

On my two Windows machines, yes, it did and then to v0.0.7

On my two Linux machines, no, they needed rebooting to get to v0.0.6 but automatically updated to v0.0.7

[Joe_H]

There are a couple of issues that can interfere with a core updating. On the server end settings or permissions can be wrong. or the core was not populated to the location needed for download. The second is sometimes a problem when a project changes from beta status to release for the Advanced setting.

On the client end, if there are more than one folding slot set for that type of folding, CPU or GPU, the update will not proceed while another slot is actively the core. Usually pausing all CPU or GPU slots will allow the update to complete when the slot requiring the new core is set to run.

Permissions issues on the client end can also the core from updating. Normally this is not a problem if the user that folding is running under has permissions set correctly, it should have R/W access to the F@h data directory.

[mwroggenbuck]

OK, my interpretation of all of this is the system should update the core, but there can be issues.

Is there any way to know what the most recent version of a core is? If that differs from what I am using, I can let the current WU finish, then force a download (remove the core from that data directory).

Like I said, I was curious about how robust the system is. Having dealt with a number of client/server projects in the past, I know this can be an interesting and challenging problem.

[Joe_H]

Overall the system is fairly robust. Actually the biggest source of errors we have seen here on the forum are user errors on the part of researchers. They forget to verify with the maintainer of the core download site that the new core has been placed in the appropriate download directory on the server and is ready to go. This has most often happened at the transition of a project requiring a new or updated core from Beta testing to release for Advanced settings in the client. It is one of a number of items on checklists that have been created for them, it just gets overlooked every so often.

Whatever version you see listed for cores A7 and 21 in the log file should be the most recent. Both finished development years ago. The A7 core was only updated last Fall due to an error found on how it handled frequent WU pauses and restarts on Windows that blew up the size of the upload file after finishing.

Core 22 is under active development as you can see here on the forum. The current full release version is 0.0.5, newer versions are in Beta testing.

[bruce]

Bottom line: If you are assigned a WU that needs a new FAHCore, it should download automatically. If you don't need the new core, it's likely NOT going to be download. Either way, you don't have to worry about it.

When there is a new Client, it will not be downloaded automatically ... you have to install it.

[mwroggenbuck]

Very good. Thanks for all the information. My curiosity has been satisfied. Fortunately, I am not a cat, so it did not cost me anything.

[JimboPalmer]

I wish to stress, you won't get the new core until you get a new WU.

'Recently', Core_22 0.0.0.5 replaced Core_22 0.0.0.2 and two of my GPUs got the new version rapidly, my third GPU did not get the new version for a week, it just never received a 'new' WU.

'Soon' Core_22 0.0.0.7 will replace it, once WUs for that version hit production. (depending on how many bugs in Beta, the version might be higher)