Team Project Contributions

[petenish]

We're very new to FAH, so maybe this question has been asked/answered and we apologize up front for that
(and please point us to the relevant posting - and sorry to be a bother).

We're curious if there is a way to get a list of all projects for a particular team has contributed a WU.
My team is interested in which projects they may have contributed some time on, as we can look
up the project, but, after a bunch of WU's (not many for our team) what we might have been working on.

Thanks for any answer, and thanks for all your folks efforts (and patience)

[PantherX]

Welcome to the F@H Forum petenish,

Please note that the information you're after isn't available officially. However, if your team members use HFM.NET (viewtopic.php?f=14&t=9903) which keeps a local copy of what WUs you have done, it would be possible.

[petenish]

That seems to only be a monitoring program of a current running system/WU.
We were looking for historical info - what WU's our team has already completed.
I was hoping there was a query to <whatever> database that might be able to
extract such information, but it sounds like, "officially", there isn't any.

Is there an "unofficial" way to get such info?

[PantherX]

Only if your team had maintained a history using HFM.net... otherwise there's no way

I am aware that in a perfect world, the Stats system would provide a lot more information, potentially what you're asking for... back in reality, with very limited resources (a single developer) that is not a high priority at all

[petenish]

Ah, well. Bummer city.
Thanks anyway for the answer.

[Neil-B]

The data you are looking for is in the logs ... if you want help post back and I'll write up a quick guide ... there are some time limitations linked to a log count "limit" but this can be extended ... you can get into huge amounts of detail (I track every WU) or simple summary stuff but it with probably take a bit of mandraulic spreadsheet work unless you have someone who wants to script it which probably wouldn't be hard.

[petenish]

Oh, that'd be swell. I don't mind rooting through logs and stuff like that. I wasn't really
aware they might be stored somewhere (makes sense).

Thanks!

[PantherX]

In the FAHClient directory, there's a folder called logs and it stores the last 16 logs by default. A new log is generated whenever the client is restarted.

[Neil-B]

Search the logs for ":Project:" this appears at the start of every WU run and has the PRCG details that can be used to "track" what is done … Client can have a log-rotate-max client option set (Expert tab of Configure in Advanced controller) which I know works up to at least 99 (as that is what I have my clients set at which reduces the chances of losing logs "off the end".

[petenish]

Yep, found the logs and was looking for good keywords. This is a help.
Also, can you point me to the set of available options? I'm slogging through
the main web pages, but they're kind of minimal.

[petenish]

ooooh, I think FAHClient --help does the trick. Is that it?

[PantherX]

Please look at this post "11 - Adding Slot Options In V7" here: viewtopic.php?f=15&t=26036

[petenish]

Thanks!

[Neil-B]

If you grab the whole line with the ":project:" in it and paste it into https://apps.foldingathome.org/wu#proje ... e=9&gen=15 it is quicker than crawling through the logs for the final upload status reports which look a bit like this

Code: Select all

03:59:00:WU02:FS00:Upload complete
03:59:00:WU02:FS00:Server responded WORK_ACK (400)
03:59:00:WU02:FS00:Final credit estimate, 10914.00 points
03:59:00:WU02:FS00:Cleaning up

... as the WU these refer to is only mentioned at the start of each upload like this

Code: Select all

03:58:54:WU02:FS00:Sending unit results: id:02 state:SEND error:NO_ERROR project:14592 run:79 clone:0 gen:10 core:0xa7 unit:0x0000000a0d5262775e7cee70fa7b1ccb
03:58:54:WU02:FS00:Uploading 3.24MiB to 13.82.98.119
03:58:54:WU01:FS00:Starting

... which also tends to be mixed in with the startup of the next WU.

Using WU status actually give you the precise points awarded for the WU or other information like "Faulty 2, or Dumped, etc." but these only show once the WUs are actually inbound processed by the WS.