// DBOINCP-300: added node comment count condition in order to get Preview working ?>
Dennis Murray
Joined: 14 Aug 10
Posts: 2
Credit: 856300
RAC: 0
17 Aug 2010 15:01:03 UTC
Topic 195255
(moderation:
)
I noticed that the names of two currently running tasks are identical and that the times elapsed and to completion are identical. This seems like a duplication of effort. Shouldn't I abort one?
I noticed that the names of two currently running tasks are identical and that the times elapsed and to completion are identical. This seems like a duplication of effort. Shouldn't I abort one?
Are you sure they are identical? Your Intel-MAC has (according to E@H website) two tasks, but the id's differ: one is *401* and the other *402*.
I noticed that the names of two currently running tasks are identical and that the times elapsed and to completion are identical. This seems like a duplication of effort. Shouldn't I abort one?
Are you sure they are identical? Your Intel-MAC has (according to E@H website) two tasks, but the id's differ: one is *401* and the other *402*.
Yup, they are different. But not by much, as the 401 and 402 indicates they are nearby in a parameter that specifies celestial/sky position. As discussed, oooh ..... well over a year ago now, the behaviour of work units in runtime along the axis of this parameter approximates a sinusoid ( or parabola maybe ). There's quite a clustering of workunits near the minimum of that curve - meaning they will have very close runtimes on a given machine - and possibly equal runtimes for a pair if each is exactly an equal 'distance' from the minimum. In this case the 'true' runtime minimum would lie b/w the sky positions indicated by 401 and 402.
You see, the sky is analysed in a pattern which would look like tiny little grid squares - if it was marked out for you while looking up at the stars - but this grid is indexed by angular position. The short answer is that one can't neatly wrap a flat newspaper around a basketball without distorting one or both, and the sinusoid mentioned above is a consequence of the choice of the marking out, and the alignment of, the grid that we calculate with.
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
identical tasks running?
)
Are you sure they are identical? Your Intel-MAC has (according to E@H website) two tasks, but the id's differ: one is *401* and the other *402*.
Task1
Task2
Michael
Team Linux Users Everywhere
Alas this is the problem
)
Alas this is the problem encountered by 59 year olds when their visual focusing acumen deteriorates. Thanks for your quick response. All is well.
RE: RE: I noticed that
)
Yup, they are different. But not by much, as the 401 and 402 indicates they are nearby in a parameter that specifies celestial/sky position. As discussed, oooh ..... well over a year ago now, the behaviour of work units in runtime along the axis of this parameter approximates a sinusoid ( or parabola maybe ). There's quite a clustering of workunits near the minimum of that curve - meaning they will have very close runtimes on a given machine - and possibly equal runtimes for a pair if each is exactly an equal 'distance' from the minimum. In this case the 'true' runtime minimum would lie b/w the sky positions indicated by 401 and 402.
You see, the sky is analysed in a pattern which would look like tiny little grid squares - if it was marked out for you while looking up at the stars - but this grid is indexed by angular position. The short answer is that one can't neatly wrap a flat newspaper around a basketball without distorting one or both, and the sinusoid mentioned above is a consequence of the choice of the marking out, and the alignment of, the grid that we calculate with.
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal