Concerning updated versions...

Author	Message
` Send message Joined: 21 Oct 06 Posts: 254 Credit: 56,691 RAC: 0	Message 46172 - Posted: 14 Sep 2007, 5:34:23 UTC I'm curious as to whether it is in the best interests of the project to abort any older versions that are in queue when an updated one becomes available? For example: 5.78 --> 5.80. ID: 46172 · Rating: 0 · rate: / Reply Quote

Greg_BE Send message Joined: 30 May 06 Posts: 5691 Credit: 5,859,226 RAC: 0	Message 46178 - Posted: 14 Sep 2007, 9:13:10 UTC - in response to Message 46172. i would think not, the data is still needed despite the version difference. I'm curious as to whether it is in the best interests of the project to abort any older versions that are in queue when an updated one becomes available? For example: 5.78 --> 5.80. ID: 46178 · Rating: 0 · rate: / Reply Quote

Mod.Sense Volunteer moderator Send message Joined: 22 Aug 06 Posts: 4018 Credit: 0 RAC: 0	Message 46194 - Posted: 14 Sep 2007, 13:26:30 UTC If you have had some specific problem with the older version would be the only case I can think of where I'd recommend aborting all the old tasks. Rosetta Moderator: Mod.Sense ID: 46194 · Rating: 0 · rate: / Reply Quote

` Send message Joined: 21 Oct 06 Posts: 254 Credit: 56,691 RAC: 0	Message 46255 - Posted: 15 Sep 2007, 7:10:04 UTC - in response to Message 46178. Last modified: 15 Sep 2007, 7:17:45 UTC Thank you to the both of you for the replies. I haven't had any problems. I was kicking the question around in my head and decided to fire the question off in here. If you have had some specific problem with the older version would be the only case I can think of where I'd recommend aborting all the old tasks. Yes, I agree that the data is needed. But would the work units that I abort be reissued to be crunched with the newest (and with the assumption "better") version? Or perhaps the project would like to have the results back ASAP regardless of version to utilize the results. i would think not, the data is still needed despite the version difference. I'm curious as to whether it is in the best interests of the project to abort any older versions that are in queue when an updated one becomes available? For example: 5.78 --> 5.80. ID: 46255 · Rating: 0 · rate: / Reply Quote

Mod.Sense Volunteer moderator Send message Joined: 22 Aug 06 Posts: 4018 Credit: 0 RAC: 0	Message 46290 - Posted: 15 Sep 2007, 17:44:10 UTC You are correct that is you aborted a task, it would be reassigned to another user to crunch. However, I believe once a given task is cut on the server, it already has a given Rosetta version associated with it. So the user that picks it up would still be told to crunch it with the same version you were given. Another way to say that is that the Rosetta version number for a given WU cannot be changed. At least that is my observation. Rosetta Moderator: Mod.Sense ID: 46290 · Rating: 0 · rate: / Reply Quote

` Send message Joined: 21 Oct 06 Posts: 254 Credit: 56,691 RAC: 0	Message 46322 - Posted: 16 Sep 2007, 3:23:26 UTC - in response to Message 46290. Last modified: 16 Sep 2007, 3:24:15 UTC That is the answer I was looking for. Thanks once again. snip Another way to say that is that the Rosetta version number for a given WU cannot be changed. At least that is my observation. ID: 46322 · Rating: 0 · rate: / Reply Quote