I don't have a lot of v 1.03 left on this one machine so I won't mind aborting them - I just normally avoid that until "last resort" presents itself.
But does that also mean these 30 some-odd Pending v 1.03s should be aborted too?
Or just waited out for available wingmen that the Server will eventually *find?
I did just refresh cache and have a supply of v 1.04 - as well as same on 2 other machines now
And the first 3 v1.04 on machine #1 are Pending rt off the bat now too.
I'm happy to share your "abort existing un-processed tasks in cache that are earlier than v 1.04" along to my Team if you advise appropriate
But does that also mean these 30 some-odd Pending v 1.03s should be aborted too?
You can't abort a task already returned to the server. They will be matched up and validated in due course.
Quote:
Or just waited out for available wingmen that the Server will eventually *find?
Exactly!!
Quote:
I'm happy to share your "abort existing un-processed tasks in cache that are earlier than v 1.04" along to my Team if you advise appropriate
If a task has already started and is partly processed, just let it finish. If there are V1.03 (or earlier) tasks that haven't started yet, abort them, return them and get an equal number of replacements. These will all be V1.04 and you wont have lost a single second of processing time. If suddenly a further new version were to appear (say V1.05) it would be because of some flaw discovered in V1.04 and I would give the same advice in that (currently hypothetical) case as well. In these testing situations, you always want to be running the current version if possible.
Doing this should more quickly assist with the testing of whatever changes were made in the new version. Ultimately, this should help get the app out of beta test status sooner.
Hi, There will be wingmen assigned soon for validation?
Yes, there will. The run seems to have moved beyond test status so there will be a very large increase in hosts to provide quorum partners.
Quote:
Have others received credit yet on the Gravitational Waves 1.04?
I certainly have. I have around 30 validated tasks of which about 5 so far are 1.04.
It's actually a bit rude to put simple queries like these in bold. It's a bit like saying, "Hello!! You guys have a problem and you don't seem to be paying attention!! Why aren't you doing something about this??", when there isn't a 'problem' at all. It's just the way things are.
The shortage of 'wingmen' has already been explained and credit will flow quite soon now as the take-up of tasks has increased dramatically. Just a little more patience is needed.
Quote:
All tasks for computer 12198550
....
The easiest way to show what you want to show is NOT to copy and paste the whole web page (and perhaps overwhelm readers with smaller screens) but rather to provide a simple link - like this one.
When you are composing a message, there are standard buttons (at the top) you can use. Also, there is a "Use BBCode tags ..." link which will give examples on how to use various features.
No wingmen on all of these(31) Gravitational Wave search O1 v 1.
)
Locality scheduling.
Read here for an explanation.
)
Read here for an explanation.
Cheers,
Gary.
Hey thanks Gary. I don't
)
Hey thanks Gary.
I don't have a lot of v 1.03 left on this one machine so I won't mind aborting them - I just normally avoid that until "last resort" presents itself.
But does that also mean these 30 some-odd Pending v 1.03s should be aborted too?
Or just waited out for available wingmen that the Server will eventually *find?
I did just refresh cache and have a supply of v 1.04 - as well as same on 2 other machines now
And the first 3 v1.04 on machine #1 are Pending rt off the bat now too.
I'm happy to share your "abort existing un-processed tasks in cache that are earlier than v 1.04" along to my Team if you advise appropriate
RE: But does that also mean
)
You can't abort a task already returned to the server. They will be matched up and validated in due course.
Exactly!!
If a task has already started and is partly processed, just let it finish. If there are V1.03 (or earlier) tasks that haven't started yet, abort them, return them and get an equal number of replacements. These will all be V1.04 and you wont have lost a single second of processing time. If suddenly a further new version were to appear (say V1.05) it would be because of some flaw discovered in V1.04 and I would give the same advice in that (currently hypothetical) case as well. In these testing situations, you always want to be running the current version if possible.
Doing this should more quickly assist with the testing of whatever changes were made in the new version. Ultimately, this should help get the app out of beta test status sooner.
Cheers,
Gary.
OK. Thanks for the
)
OK. Thanks for the confirmations
Well I accidentally aborted 3 v 1.03s that were currently crunching - didn't see them on opposite side of page(out of view)
So 17 Total is all I had in my queue - out they went - the 3 partials and 14 others. not bad, but sorry for three that got trashed.
Thanks again for the Explain and what to do
Hi, There will be wingmen
)
Hi, There will be wingmen assigned soon for validation?
Have others received credit yet on the Gravitational Waves 1.04?
Thanks, Stu D.
All tasks for computer 12198550
Stu D. · log out
State: All (19) · In progress (6) · Validation pending (11) · Validation inconclusive (2) · Valid (0) · Invalid (0) · Error (0)
Application: All (19) · Binary Radio Pulsar Search (Arecibo) (0) · Binary Radio Pulsar Search (Arecibo, GPU) (0) · Binary Radio Pulsar Search (Parkes PMPS XT) (0) · Gamma-ray pulsar binary search #1 (0) · Gamma-ray pulsar search #4 (0) · Gravitational Wave search O1 all-sky tuning (19)
Task name:
OK
Task
click for details
Show names Work unit
click for details Sent Time reported
or deadline
explain Status Run time
(sec) CPU time
(sec) Credit Application
546615758 240179394 21 Feb 2016, 15:47:51 UTC 28 Feb 2016, 15:47:51 UTC In progress --- --- --- Gravitational Wave search O1 all-sky tuning v1.04 (AVX)
windows_x86_64
546615760 240179395 21 Feb 2016, 15:47:51 UTC 28 Feb 2016, 15:47:51 UTC In progress --- --- --- Gravitational Wave search O1 all-sky tuning v1.04 (AVX)
windows_x86_64
546615752 240179391 21 Feb 2016, 15:47:50 UTC 28 Feb 2016, 15:47:50 UTC In progress --- --- --- Gravitational Wave search O1 all-sky tuning v1.04 (AVX)
windows_x86_64
546615754 240179392 21 Feb 2016, 15:47:50 UTC 28 Feb 2016, 15:47:50 UTC In progress --- --- --- Gravitational Wave search O1 all-sky tuning v1.04 (AVX)
windows_x86_64
546615756 240179393 21 Feb 2016, 15:47:50 UTC 28 Feb 2016, 15:47:50 UTC In progress --- --- --- Gravitational Wave search O1 all-sky tuning v1.04 (AVX)
windows_x86_64
546615748 240179389 21 Feb 2016, 15:47:49 UTC 22 Feb 2016, 23:09:23 UTC Completed, waiting for validation 27,481.51 27,410.73 pending Gravitational Wave search O1 all-sky tuning v1.04 (AVX)
windows_x86_64
546615750 240179390 21 Feb 2016, 15:47:49 UTC 28 Feb 2016, 15:47:49 UTC In progress --- --- --- Gravitational Wave search O1 all-sky tuning v1.04 (AVX)
windows_x86_64
546615746 240179388 21 Feb 2016, 5:05:45 UTC 22 Feb 2016, 12:00:09 UTC Completed, waiting for validation 27,653.13 27,542.20 pending Gravitational Wave search O1 all-sky tuning v1.04 (AVX)
windows_x86_64
546615744 240179387 20 Feb 2016, 11:29:39 UTC 22 Feb 2016, 0:22:05 UTC Completed, waiting for validation 27,488.28 27,414.05 pending Gravitational Wave search O1 all-sky tuning v1.04 (AVX)
windows_x86_64
546615742 240179386 20 Feb 2016, 0:49:31 UTC 21 Feb 2016, 13:54:30 UTC Completed, waiting for validation 27,989.75 27,761.59 pending Gravitational Wave search O1 all-sky tuning v1.04 (AVX)
windows_x86_64
546615738 240179384 19 Feb 2016, 4:04:43 UTC 20 Feb 2016, 11:29:38 UTC Completed, waiting for validation 28,226.39 27,927.51 pending Gravitational Wave search O1 all-sky tuning v1.03 (AVX)
windows_x86_64
546615740 240179385 19 Feb 2016, 4:04:43 UTC 20 Feb 2016, 20:10:47 UTC Completed, waiting for validation 27,742.34 27,599.47 pending Gravitational Wave search O1 all-sky tuning v1.03 (AVX)
windows_x86_64
546615736 240179383 18 Feb 2016, 11:21:05 UTC 19 Feb 2016, 6:24:07 UTC Completed, waiting for validation 27,711.17 27,626.27 pending Gravitational Wave search O1 all-sky tuning v1.03 (AVX)
windows_x86_64
546615734 240179382 17 Feb 2016, 23:25:33 UTC 19 Feb 2016, 21:05:36 UTC Completed, waiting for validation 27,670.72 27,595.89 pending Gravitational Wave search O1 all-sky tuning v1.03 (AVX)
windows_x86_64
546615732 240179381 17 Feb 2016, 14:41:50 UTC 18 Feb 2016, 19:59:59 UTC Completed, waiting for validation 27,750.34 27,637.89 pending Gravitational Wave search O1 all-sky tuning v1.03 (AVX)
windows_x86_64
546615728 240179379 16 Feb 2016, 16:48:04 UTC 17 Feb 2016, 14:05:06 UTC Completed, validation inconclusive 27,780.39 27,610.84 pending Gravitational Wave search O1 all-sky tuning v1.03 (AVX)
windows_x86_64
546615730 240179380 16 Feb 2016, 16:48:04 UTC 17 Feb 2016, 0:41:13 UTC Completed, waiting for validation 27,472.93 27,312.42 pending Gravitational Wave search O1 all-sky tuning v1.03 (AVX)
windows_x86_64
546615724 240179377 16 Feb 2016, 16:48:03 UTC 18 Feb 2016, 8:00:51 UTC Completed, validation inconclusive 27,062.69 26,960.59 pending Gravitational Wave search O1 all-sky tuning v1.03 (AVX)
windows_x86_64
546615726 240179378 16 Feb 2016, 16:48:03 UTC 17 Feb 2016, 22:40:07 UTC Completed, waiting for validation 27,531.32 27,304.53 pending Gravitational Wave search O1 all-sky tuning v1.03 (AVX)
windows_x86_64
RE: Hi, There will be
)
Yes, there will. The run seems to have moved beyond test status so there will be a very large increase in hosts to provide quorum partners.
I certainly have. I have around 30 validated tasks of which about 5 so far are 1.04.
It's actually a bit rude to put simple queries like these in bold. It's a bit like saying, "Hello!! You guys have a problem and you don't seem to be paying attention!! Why aren't you doing something about this??", when there isn't a 'problem' at all. It's just the way things are.
The shortage of 'wingmen' has already been explained and credit will flow quite soon now as the take-up of tasks has increased dramatically. Just a little more patience is needed.
The easiest way to show what you want to show is NOT to copy and paste the whole web page (and perhaps overwhelm readers with smaller screens) but rather to provide a simple link - like this one.
When you are composing a message, there are standard buttons (at the top) you can use. Also, there is a "Use BBCode tags ..." link which will give examples on how to use various features.
Cheers,
Gary.
Hi Gary, Thanks for the
)
Hi Gary,
Thanks for the info.
Appreciate it,
Stu
You're most welcome!
)
You're most welcome!
Cheers,
Gary.