| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Active Research
Forum: Mapping Cancer Markers Forum
Thread: One-Time Download is re-downloaded if the device runs out of work and then gets more |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 4
|
|
| Author |
|
|
ST240
Cruncher Joined: Feb 15, 2024 Post Count: 15 Status: Offline |
The System Requirements page on the website shows a one-time download of 40MB for MCM, but my devices are downloading a 46MB file (e55b6bdba4ed0b4b6e315c6767d68e3f.txt) whenever they get tasks and don't currently have any. If the device gets new tasks while it already has some, the file is not downloaded. If the device runs out of tasks, the file disappears from the BOINC project directory.
|
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7846 Status: Offline Project Badges: 
|
The System Requirements page on the website shows a one-time download of 40MB for MCM, but my devices are downloading a 46MB file (e55b6bdba4ed0b4b6e315c6767d68e3f.txt) whenever they get tasks and don't currently have any. If the device gets new tasks while it already has some, the file is not downloaded. If the device runs out of tasks, the file disappears from the BOINC project directory. Yes, unfortunately that is the way it works. Frustrating as all get out especially since the current state of MCM availability is sporadic. Some of my Linux machines are doing this several times a day as they run out, get more, run out, etc. several times a day. With a steady supply of MCM this behavior is not present. You would think the powers that be could make this file sticky so it would not disappear when the supply of MCM runs out. Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2346 Status: Recently Active Project Badges: 
|
From post 453284 (Apr 1, 2014) by Seippel:
"Work unit files are categorized into three different types: 1) Files which are specific to a single work unit. … 2) File(s) which span a large number of work units but not the life of the project. These files are downloaded once, but deleted from the client machine once all work units that need it are finished. The MCM1 dataset files fall into this category. 3) Files which are needed by all work units (or nearly all) work units for a project. …" As Sgt.Joe wrote: that's the way it works. Adri |
||
|
|
ST240
Cruncher Joined: Feb 15, 2024 Post Count: 15 Status: Offline |
Okay, thanks.
|
||
|
|
|