 |
|
Message boards : Number crunching : Batches closed
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 5 Sep 04 Posts: 7629 Credit: 24,240,330 RAC: 0 |
These batches have just been closed: 759, 795, 835, 837, 844, 876, 892, 893, 894, 916, 917, 918 |
 Send message Joined: 15 Jul 17 Posts: 99 Credit: 18,701,746 RAC: 318 |
Then what? Server abort signals? 
|
|
Send message Joined: 7 Sep 16 Posts: 262 Credit: 34,915,412 RAC: 16,463 |
I'll just ask the stupid question here: What does this mean and how do I tell if it impacts any of my active WUs? Looking at the task and workunit data for my active tasks, I don't see batch listed anywhere. |
 Dave JacksonSend message Joined: 15 May 09 Posts: 4537 Credit: 19,001,532 RAC: 21,726 |
Looking at the task and workunit data for my active tasks, I don't see batch listed anywhere. This sticky tells you what information you can glean from task names which includes the batch number which is the third number in from the Right _919_ being the most recent batch number. |
|
Dave Jackson Send message Joined: 15 May 09 Posts: 4537 Credit: 19,001,532 RAC: 21,726 |
I'll just ask the stupid question here: What does this mean and how do I tell if it impacts any of my active WUs? Unless you are very slow at completing tasks, it will not impact your work. Even if you are, I am fairly certain you can still get credit from closed batches, however by the time batches are closed, any data returned is no longer any use by the scientists. It would also mean any remaining tasks that hadn't been sent out would be cancelled however given there was no work left in the queue, that was not relevant on this occasion. I am wondering if it means that tasks returned don't get mentioned on the server status page which shows how many computers have returned tasks within the past 24 hours as since all these batches were closed, "users in past 24 hours" has been zero? |
|
Send message Joined: 5 Sep 04 Posts: 7629 Credit: 24,240,330 RAC: 0 |
What does this mean It means that the researchers are finished with those batches, so any still not returned are no longer being accepted by the relevant server. So Abort any of those that you still have. |
|
geophi Send message Joined: 7 Aug 04 Posts: 2187 Credit: 64,822,615 RAC: 5,275 |
I am wondering if it means that tasks returned don't get mentioned on the server status page which shows how many computers have returned tasks within the past 24 hours as since all these batches were closed, "users in past 24 hours" has been zero? I think that's because the transitioner isn't running. I'm sure someone has completed hadam4h, hadam4, hadsm4 or wah2 tasks in the last 24 hours. |
|
Dave Jackson Send message Joined: 15 May 09 Posts: 4537 Credit: 19,001,532 RAC: 21,726 |
I think that's because the transitioner isn't running. I'm sure someone has completed hadam4h, hadam4, hadsm4 or wah2 tasks in the last 24 hours. Clearly you are right George, now transitioner running again, server status updates have been happening. |
|
Send message Joined: 29 Oct 17 Posts: 1049 Credit: 16,432,494 RAC: 17,331 |
The following OpenIFS batches have now been closed: 944, 945, 946, 947, 990. These batches were issued in Nov/22. If you have any tasks still running or waiting to run from these batches please Abort them. It is not CPDN policy to remotely abort workunits on volunteer computers. A closed batch means the project has enough returned results and any remaining uploads will be discarded. The batch name can be determined from the task name e.g. oifs_a002_201312_25_994_012039265_2. For more details on task naming, see this post. --- CPDN Visiting Scientist |
|
Send message Joined: 29 Oct 17 Posts: 1049 Credit: 16,432,494 RAC: 17,331 |
The following hadam4h batches for the ArctiCONNECT project have now been closed: 931, 932. These batches were issued in June/22. If you have any tasks still running or waiting to run from these batches please Abort them. It is not CPDN policy to remotely abort workunits on volunteer computers. A closed batch means the project has enough returned results and any remaining uploads will be discarded. The batch name can be determined from the task name e.g. *_a002_201312_25_994_012039265_2. For more details on task naming, see this post. |
|
Send message Joined: 29 Oct 17 Posts: 1049 Credit: 16,432,494 RAC: 17,331 |
The following hadsm4 batches for the DOCILE project have now been closed: 937, 938, 939, 940, 941. These batches were issued in Nov/22. If you have any tasks still running or waiting to run from these batches please Abort them. It is not CPDN policy to remotely abort workunits on volunteer computers. A closed batch means the project has enough returned results and any remaining uploads will be discarded. The batch name can be determined from the task name e.g. *_a002_201312_25_994_012039265_2. |
|
Dave Jackson Send message Joined: 15 May 09 Posts: 4537 Credit: 19,001,532 RAC: 21,726 |
I noticed a sudden big drop in the number of tasks ready to send. Have some of the current batches been cancelled? |
|
Send message Joined: 29 Oct 17 Posts: 1049 Credit: 16,432,494 RAC: 17,331 |
See my post in the EAS 1001-1004 thread. Copied here. EAS Batches 1002, 1003, 1004 have been closed An error in the production of the files used by these batches has been found and the results are not scientifically accurate. These batches have been closed, the error will be corrected and the batches resubmitted. You can kill any tasks currently running with these batch numbers. The batch number can be found in the task title as the second to last number. e.g. wah2_eas25_h000_200912_24_1002_012229966 is for batch 1002. Batch 1001 is unaffected, please keep these tasks running! --- CPDN Visiting Scientist |
|
Dave Jackson Send message Joined: 15 May 09 Posts: 4537 Credit: 19,001,532 RAC: 21,726 |
See my post in the EAS 1001-1004 thread. Copied here.Spotted that seconds after posting! |
 Send message Joined: 2 Oct 06 Posts: 54 Credit: 27,309,613 RAC: 28,128 |
It is not CPDN policy to remotely abort workunits on volunteer computers. This is a bad policy, and needs to be changed. If the project is not going to use the results of any tasks out in the wild, they should be aborted from the server side. Otherwise electricity and time are just be wasted. Seems contrary to the goal of CPDN, right? |
|
Send message Joined: 14 Sep 08 Posts: 127 Credit: 41,662,895 RAC: 61,039 |
This is a bad policy, and needs to be changed. If the project is not going to use the results of any tasks out in the wild, they should be aborted from the server side. Otherwise electricity and time are just be wasted. Seems contrary to the goal of CPDN, right? Agreed. I'd rather server abort these immediately. Given the trickling mechanism, even if it's for credits, it won't affect people's contribution. Can't think of a reason of not aborting them... |
|
Send message Joined: 29 Oct 17 Posts: 1049 Credit: 16,432,494 RAC: 17,331 |
The following OpenIFS batches for the STORMS project have now been closed: 1016, 1017, 1018. The success rate was 98% and the project scientist in Finland is pleased with the results. Thanks to all those who computed these batches. --- CPDN Visiting Scientist |
|
Send message Joined: 29 Oct 17 Posts: 1049 Credit: 16,432,494 RAC: 17,331 |
The Weather@Home New Zealand domain NZ25 batch 1005 has now been closed. This batch was launched 23rd Jan 2024. The batch size was 4650 workunits and the success rate on this batch was 92%. Thanks to all who contributed results. Closing a batch means no further resends will go out for any failed tasks. Running tasks can finish, the results will be used and credit given. --- CPDN Visiting Scientist |
©2024 cpdn.org
