Units in queue

[Yoste]

Hi, I've got a question about the queue...
Is it possible to put some WU's in the queue so my pc can work on them when not connected to the internet for a while?

Thanks for the help!

Yoste

[toTOW]

No, the queue is not made to cache work. It's intended to cache results if the work server can't accept them temporarily (due to network or server outage).

Please read this article about caching WU (it's no longer possible) : http://fahwiki.net/index.php/WorkUnits# ... Work_Units

[Yoste]

Thanks, think I just won't fold for a while then ...

[smoking2000]

It's intended to cache results if the work server can't accept them temporarily (due to network or server outage).

That's not true. The queue.dat only contains meta data of the Work Unit, a collection of information it gets from the Assignment Server, FAH client configuration and Work Unit data, which is written to the queue.dat when the FAH client starts a new WU. The FAH client uses the queue.dat to keep track of WUs and their state, like which servers to return the WU to, how many upload failures have occurred, etc. The WU results are stored in the work/wuresults_??.dat file if the Work and Collection Servers are unable to accept the work.

See: http://fahwiki.net/index.php/FAH_files

[7im]

You are splitting hairs smoking2000. They said queue, not queue.dat. Those two things are different, so toTOW didn't get it wrong, he just didn't go in to the detail that you did. The client does have a queueing ability, made up of several different components, most of which are mentioned above.

And in the interest of giving more detail, the client did have the ability to cache up to 10 work units in the past, when there were Timeless work units. Sorry, no more Timeless (deadlineless) work units, so no more caching of fah work units.

[bruce]

Sorry, no more Timeless (deadlineless) work units, so no more caching of fah work units.

Thanks, think I just won't fold for a while then ...

The scientific needs of the FAH project REQUIRE that WUs are returned promptly, and caching is inconsistent with those needs. If you can't return the results promptly, they'd rather that you didn't download the WU at all.

The meaning of the word "promptly" varies somewhat. Projects for the uniprocessor client have much longer deadlines than projects for the high-performance clients (GPU, SMP, PS3). The deadlineless WUs (which actually had deadlines that were much longer than the present uniprocessor client) were discontinued because they did not meet the requirements of FAH's science.

[smoking2000]

You are splitting hairs smoking2000.

Just making sure there is no miss information spread by our new mod.

[bruce]

Just making sure there is no miss information spread by our new mod.

We all try to make sure that there is no misinformation spread by ANYONE on this forum. .

[anko1]

Aside from the queue question, isn't it true that the computer works on the unit even when it's not connected to the internet, so that Yoste could still make contributions assuming that s/he connected to the internet at reasonable intervals to send back the work? If s/he's disconnected for a week, that may not fly, but if it's only for a day, would that make sense?

[bruce]

Aside from the queue question, isn't it true that the computer works on the unit even when it's not connected to the internet, so that Yoste could still make contributions assuming that s/he connected to the internet at reasonable intervals to send back the work? If s/he's disconnected for a week, that may not fly, but if it's only for a day, would that make sense?

Yes, that makes sense to me but I'm not sure if that solves Yoste's concerns.