A work unit from project 10473 wrong display %

[JaredKFan]

Hi, I just started a work unit from project 10473. Both the advanced client and the web client display this work unit as folding very slowly (it does not even appear to be at 1% yet) based on the control panels' display. But checking the log shows it folding at the speed it is supposed to (I have dual geforce gtx 980 cards and both are being used for folding in addition to the CPU, which is also a fast one) The log shows it to be making 1% percent progress every four minutes or so. So I am not sure if the FAH windows graphical client and web client are displaying the completed percentage of the work unit incorrectly or if some other thing is at fault.

Edit: Now it seems to be displaying correctly. Does it take a few minutes sometimes for the text log and graphical/web clients to be in sync?

Jared

[7im]

Yes.

[Rel25917]

the first time you run a unit from each project the client wont know the progress until a checkpoint is written. This can take anywhere from 1 to 10 or 20 percent(selected by the researcher when the the project is made.) After the client has an idea of the time per frame it should be fairly accurate but it is still a guess by the client and is updated every time a new checkpoint is written.

[davidcoton]

the first time you run a unit from each project the client wont know the progress until a checkpoint is written. This can take anywhere from 1 to 10 or 20 percent(selected by the researcher when the the project is made.) After the client has an idea of the time per frame it should be fairly accurate but it is still a guess by the client and is updated every time a new checkpoint is written.

I don't think that is quite right. Progress is reported every 1% (at least in most projects), and FAHControl tries to guess progress in between. Frame times can also vary quite a lot between frames. This means that, with a project you haven't had before, the progress estimates are out for the first 1%, sometimes longer. It's not linked to the checkpoint interval.

[bruce]

Progress is reported TO THE LOG every 1% but not to FAHClient. By design, FAHClient does not parse the log, it looks at other internal data associated with checkpoints. Thus the progress required to generate more accurate predictions varies with the checkpoint frequency of the project but it's significantly longer than 1% unless you've processed the same project before.

[Rel25917]

It's not linked to the checkpoint interval.

Sit down and watch it run a unit from a project that it has never done before. Dig into the logs in the work unit folder and find the actual checkpoint frequency(xtc write frequency). It may be 2.5% or 5% or whatever(it is done by steps rather than %). When the first checkpoint is written all of a sudden fahclient will magically figure out the current time per frame. Coincidence? I think not. If you do anything that slows the wu processing down fahclient wont figure it out until after a checkpoint.

[davidcoton]

OK, accept that. Looks like was wrong. Situation normal