1)
Message boards :
News :
Temporarily work unavailabilities
(Message 2437)
Posted 27 Mar 2025 by hoarfrost Post: The queue is exhausted at this moment. Hi Greg! Because these were the last tasks. There won't be any new ones for a while. |
2)
Message boards :
Number crunching :
upload server troubles - transient HTTP error
(Message 2428)
Posted 4 Mar 2025 by hoarfrost Post: Hello! Looks like network outages. Server load is constant (in average) and not great for it. |
3)
Message boards :
News :
Temporarily work unavailabilities
(Message 2408)
Posted 27 Jan 2025 by hoarfrost Post: Hi folks! Greg, thank you for message. We have started creating new tasks for x86, for target # 11, "corona_Sprot_delta_v1", in parallel to ARM-tasks. They will be relatively short and the queue of tasks may be exhausted sometimes. Good luck! |
4)
Message boards :
News :
Temporarily work unavailabilities
(Message 2388)
Posted 31 Dec 2024 by hoarfrost Post: May be useful for running ARM application: ARM Linux App. |
5)
Message boards :
Number crunching :
SiDock@home is not F1...
(Message 2367)
Posted 14 Dec 2024 by hoarfrost Post: I read there is adaptive replication to deal with these cases. https://github.com/BOINC/boinc/wiki/Adaptive-Replication It is a good idea. Values from template can be overrided for some fraction of workunits during tasks generation. |
6)
Message boards :
News :
Target # 23: Ebola GP1
(Message 2365)
Posted 13 Dec 2024 by hoarfrost Post: You have anticipation of when lots of x86 work will resume? I don't know. We doesn't have next target, simply. |
7)
Message boards :
Number crunching :
SiDock@home is not F1...
(Message 2362)
Posted 9 Dec 2024 by hoarfrost Post: So someone was cheating Sidock credits to win some silly competition? Looks that someone tried to convert competition to silly thing. A ridiculous story comes to mind in such cases: Bear, wolf, fox and hare are playing cards. A bear says: "Don't cheat! Whoever cheats will get a kick by brazen auburn muzzle!" Good luck! |
8)
Message boards :
News :
Target # 23: Ebola GP1
(Message 2356)
Posted 9 Dec 2024 by hoarfrost Post: An explanation is needed, of course. At this moment we have two applications: "Longs tasks" and "short tasks". Applications identical by sense and source code. For "Long tasks" we perform generation of tasks for main search that need much more CPU time per task. We send these to computers with x86-64 platform. Workunits for "Short tasks" much more shorter due to properties of target and search goals. We send these to ARM-based computers. Now don't have another target right now. After ending of "ebola_GP_v1" we will try return to generation of "Short tasks" for x86-64 platform, but presumably, they won't be enough for full load. |
9)
Message boards :
Number crunching :
SiDock@home is not F1...
(Message 2352)
Posted 8 Dec 2024 by hoarfrost Post: ... and we will be fining fairly. >:D Initial Replication == 1 allows us to shows our best and worst sides, but option # 1 is preferable due to: 1. Relationships to other participants; 2. There is a bear's paw for every cunning fox; 3. My script is much more might. 43, ... |
10)
Message boards :
News :
Target # 23: Ebola GP1
(Message 2338)
Posted 30 Nov 2024 by hoarfrost Post: As I write Target 23 is 75.501% complete. Will be interesting to see what the next Target we work on will be Hello! It looks like there will be ARM-only tasks for a while. |
11)
Message boards :
Number crunching :
MacOS support?
(Message 2331)
Posted 7 Nov 2024 by hoarfrost Post: Hello! We don't have a Mac app. |
12)
Message boards :
News :
Target # 22: corona_RdRp_v2
(Message 2315)
Posted 11 Sep 2024 by hoarfrost Post: Hi! Yes, first portion of workunits have 1 day deadline, subsequent workunits must get 2 days deadline. Required settings already applied. |
13)
Message boards :
Number crunching :
Stats export
(Message 2313)
Posted 11 Sep 2024 by hoarfrost Post: Fixed. Thank you! |
14)
Message boards :
News :
Target # 22: corona_RdRp_v2
(Message 2311)
Posted 1 Sep 2024 by hoarfrost Post: Any way to split the requirement into smaller segments? that target 1.5 to 2 hour runtimes?? Expected task average computing time ~1.5 .. 3 hours, but due to nature of new target, not workunits splitting. |
15)
Message boards :
News :
Target # 23: Ebola GP1
(Message 2305)
Posted 27 Aug 2024 by hoarfrost Post: Hello! Sample workunits for target "ebola_GP_v1" issued. They will be followed by a tail of "corona_RdRp_v2" tasks. Thank you for participation! |
16)
Message boards :
News :
Target # 23: Ebola GP1
(Message 2298)
Posted 16 Jul 2024 by hoarfrost Post: What is the estimation of the end date of corona_RdRp_v2 ? One or two months, I expect. |
17)
Message boards :
News :
Target # 22: corona_RdRp_v2
(Message 2297)
Posted 16 Jul 2024 by hoarfrost Post: Hello! The next target will be processed on CPU only and it will be much shorter. Hope that Marko tell about scientific background. |
18)
Message boards :
Number crunching :
No short tasks
(Message 2290)
Posted 11 Jul 2024 by hoarfrost Post: Is it ok if i run short tasks using app_info.xml and compiled cmdock? Yes. What keys you use for application compilation? |
19)
Message boards :
Number crunching :
No short tasks
(Message 2274)
Posted 25 Jun 2024 by hoarfrost Post: Hello! Solved. :) |
20)
Message boards :
Number crunching :
Is it possible to turn on the setting "Max # of simultaneous tasks" ?
(Message 2255)
Posted 21 Apr 2024 by hoarfrost Post: Hello! :) Presumably, BOINC should balance everything after gathering statistics for tasks calculations. Give it one or two weeks of work. |
©2025 SiDock@home Team