Thank you very much for the information. Such openess of whats happening, shows that Einstein is in control of very dedicated, clever and open minded people. Keep up the good work.
Thank you very much for the information. Such openess of whats happening, shows that Einstein is in control of very dedicated, clever and open minded people. Keep up the good work.
Best regards
Bent, Oslo, Norway
I agree with you, completely.
Being on top of things is the best. Communicating is the best, too. And keeping me from wasting energy and money by being on top of things and communicating is the best, too.
how should we handle with every time is announced a new list of canceled beams?
Should we every time kill our local cache for brp4g WU's to prevent doing work for the basket?
I'm pretty sure I've seen the bad tasks will be automatically canceled when your host contacts the server or if you hit the update. There's no need for manual managing.
thats the reason why I'm asking here. I saw in the last days that even a Host had have Contact with the Projectservers no one of the canceled WU's was deleted in the Cache of the Hosts. As far as I can remember Reading in another Post, this Function for this kind of WU's is not activ on the Server side atm.
My mistake, I had to read that exactly, but the question is still the same. How can we handle that in the future?
Thank you very much for the
)
Thank you very much for the information. Such openess of whats happening, shows that Einstein is in control of very dedicated, clever and open minded people. Keep up the good work.
Best regards
Bent, Oslo, Norway
RE: Thank you very much for
)
I agree with you, completely.
Being on top of things is the best. Communicating is the best, too. And keeping me from wasting energy and money by being on top of things and communicating is the best, too.
Thanks Einstein@Home team.
There was another badge of
)
There was another badge of bad beams that I just canceled:
p2030.20151214.G175.58-01.91.S.b5s0g0.00000
p2030.20151214.G175.72-01.70.C.b0s0g0.00000
p2030.20151214.G175.72-01.70.C.b2s0g0.00000
p2030.20151214.G175.72-01.70.C.b3s0g0.00000
p2030.20151214.G175.72-01.70.C.b4s0g0.00000
p2030.20151214.G175.72-01.70.C.b5s0g0.00000
p2030.20151214.G175.72-01.70.C.b6s0g0.00000
p2030.20151214.G176.01-01.26.S.b1s0g0.00000
p2030.20151214.G175.72-01.70.C.b1s0g0.00000
And here is another badge of
)
And here is another badge of bad beams:
I just canceled the following
)
I just canceled the following beams:
p2030.20151219.G177.98+00.55.C.b1s0g0.00000
p2030.20151219.G177.98+00.55.C.b3s0g0.00000
p2030.20151219.G177.56-00.11.C.b4s0g0.00000
p2030.20151219.G177.56-00.11.C.b5s0g0.00000
p2030.20141111.G190.64-01.16.N.b4s0g0.00000
p2030.20141115.G191.17-01.14.C.b3s0g0.00000
p2030.20151215.G177.42+00.52.C.b4s0g0.00000
p2030.20151216.G177.42+00.09.C.b2s0g0.00000
p2030.20151216.G177.42+00.09.C.b5s0g0.00000
p2030.20151219.G177.98+00.55.C.b0s0g0.00000
p2030.20151219.G177.98+00.55.C.b6s0g0.00000
I just canceled the following
)
I just canceled the following beams:
p2030.20151219.G177.56-00.11.C.b0s0g0.00000
p2030.20151219.G177.56-00.11.C.b2s0g0.00000
p2030.20141122.G192.21-00.19.S.b0s0g0.00000
p2030.20141122.G192.21-00.19.S.b1s0g0.00000
p2030.20141122.G192.21-00.19.S.b2s0g0.00000
p2030.20141122.G192.21-00.19.S.b5s0g0.00000
p2030.20141122.G192.59+00.50.S.b5s0g0.00000
p2030.20141124.G192.11-01.31.S.b0s0g0.00000
p2030.20141124.G192.11-01.31.S.b1s0g0.00000
p2030.20141124.G192.11-01.31.S.b2s0g0.00000
p2030.20141125.G193.51+00.77.S.b2s0g0.00000
p2030.20141125.G193.51+00.77.S.b3s0g0.00000
p2030.20141126.G192.39-01.74.C.b0s0g0.00000
p2030.20141126.G192.39-01.74.C.b3s0g0.00000
p2030.20141126.G192.39-01.74.C.b4s0g0.00000
p2030.20141126.G192.39-01.74.C.b5s0g0.00000
p2030.20141128.G193.04-01.05.N.b5s0g0.00000
...sadly to Late, a couple of
)
...sadly to Late, a couple of WU's are for the basket.
Thx and BR
Greetings from the North
Hi Christian, how should we
)
Hi Christian,
how should we handle with every time is announced a new list of canceled beams?
Should we every time kill our local cache for brp4g WU's to prevent doing work for the basket?
Or is there another way to identify the bad WU's without looking over the caches from all Hosts?
8 WU's from 22th also for trash!
BR
DMmdL
Greetings from the North
Der Mann mit der Ledertasche
)
I'm pretty sure I've seen the bad tasks will be automatically canceled when your host contacts the server or if you hit the update. There's no need for manual managing.
Hi Richie,thats the reason
)
Hi Richie,
thats the reason why I'm asking here. I saw in the last days that even a Host had have Contact with the Projectservers no one of the canceled WU's was deleted in the Cache of the Hosts. As far as I can remember Reading in another Post, this Function for this kind of WU's is not activ on the Server side atm.
My mistake, I had to read that exactly, but the question is still the same. How can we handle that in the future?
https://einsteinathome.org/content/wu-cancelled
BR
DMmdL
Greetings from the North