Premature announcement Stephen.
I reported 10 tasks, received five blc35 _2's

There won't be any new BLC35s issued, but of course there are probably 10s of thousands (if not 100s of thousands) of them still to be cleared out.

---

Grant
Darwin NT

we are done splitting the blc35 that have caused so many problems. I'm sure they will continue to cause issues as they are still in caches and might need more wingmen, but it should be less problems from this point. Hopefully this will give the system a chance to catch up.

. . And the Setizens bid a fond farewell to the Blc35 WUs of 58692 and 58693 with a hearty cheer ...

"RACK OFF YA NASTY, NOISY SOANDSOs"

Stephen

:)

Premature announcement Stephen.
I reported 10 tasks, received five blc35 _2's

. . They are the final validate checks for overflows on slow machines, I have a handful of _2's as well :) but almost none compared to when they were still splitting ...

Stephen

< shrug >

we are done splitting the blc35 that have caused so many problems. I'm sure they will continue to cause issues as they are still in caches and might need more wingmen, but it should be less problems from this point. Hopefully this will give the system a chance to catch up.

. . And the Setizens bid a fond farewell to the Blc35 WUs of 58692 and 58693 with a hearty cheer ...

"RACK OFF YA NASTY, NOISY SOANDSOs"

Stephen

:)

Premature announcement Stephen.
I reported 10 tasks, received five blc35 _2's

. . They are the final validate checks for overflows on slow machines, I have a handful of _2's as well :) but almost none compared to when they were still splitting ...

Stephen

< shrug >

What you say is true, but you fail to take into account the deadline, they are VLAR's, so on my latest it is 04/06/2020 (US format). So we will be seeing blc35 for some time yet.

Things are looking good for the system. We have all the WUs we want as the RTS queue is a healthy size of a couple of hours worth. It is going to take some time for the junk WUs to work their way out of the db and for the Results returned and awaiting validation to get to normal size again. Will it take 6 weeks for those blc35s to time out and plague us again??

We have caught up on Aricebo data files and are now splitting old files again. It also looks like they will have to load some Greenbank data on the splitter pile for us sometime this weekend.

I hope the seti team has a nice quiet weekend for a change.

Time to look at the data. I tried to search for TIC434234955 and came up with nothing. anyone know about the TIC files??

Time to look at the data. I tried to search for TIC434234955 and came up with nothing. anyone know about the TIC files??

https://tess.mit.edu/science/tess-input-catalogue/

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

we are done splitting the blc35 that have caused so many problems. I'm sure they will continue to cause issues as they are still in caches and might need more wingmen, but it should be less problems from this point. Hopefully this will give the system a chance to catch up.

. . And the Setizens bid a fond farewell to the Blc35 WUs of 58692 and 58693 with a hearty cheer ...

"RACK OFF YA NASTY, NOISY SOANDSOs"

Stephen

:)

. . They are the final validate checks for overflows on slow machines, I have a handful of _2's as well :) but almost none compared to when they were still splitting ...

Stephen

< shrug >

What you say is true, but you fail to take into account the deadline, they are VLAR's, so on my latest it is 04/06/2020 (US format). So we will be seeing blc35 for some time yet.

. . Well you can count all that you find on your machine/s and let me know how many continue to plague you ...

Stephen

<shrug>

Time to look at the data. I tried to search for TIC434234955 and came up with nothing. anyone know about the TIC files??

https://tess.mit.edu/science/tess-input-catalogue/

Thanks Keith!

This is data from pointing the dish at stars with exoplanets, if I'm understanding this correctly. Sounds like a good thing to do. 58838 is Dec 21, 2019. So this is also very fresh data.

Time to look at the data. I tried to search for TIC434234955 and came up with nothing. anyone know about the TIC files??

https://tess.mit.edu/science/tess-input-catalogue/

Thanks Keith!

This is data from pointing the dish at stars with exoplanets, if I'm understanding this correctly. Sounds like a good thing to do. 58838 is Dec 21, 2019. So this is also very fresh data.

. . This is very interesting. But we have data on so few exoplanets. There is so much work ahead of this project.

Stephen

. .

we are done splitting the blc35 that have caused so many problems. I'm sure they will continue to cause issues as they are still in caches and might need more wingmen, but it should be less problems from this point. Hopefully this will give the system a chance to catch up.

We have now passed 10 days since the blc35s that were so bad were last sent. I'm assuming there is still a 10 day cache size limit. So hopefully a bunch more of the blc35s have gone through the system. Now we just need to wait for the time out date for these files to finally be done with them.

edit: March 20 for one of the blc35s I still have.

we are done splitting the blc35 that have caused so many problems. I'm sure they will continue to cause issues as they are still in caches and might need more wingmen, but it should be less problems from this point. Hopefully this will give the system a chance to catch up.

We have now passed 10 days since the blc35s that were so bad were last sent. I'm assuming there is still a 10 day cache size limit. So hopefully a bunch more of the blc35s have gone through the system. Now we just need to wait for the time out date for these files to finally be done with them.

If they report before the deadline, won't the deadline just trigger the sending of the _2 task and then the deadline for those...........

edit: March 20 for one of the blc35s I still have.

we are done splitting the blc35 that have caused so many problems. I'm sure they will continue to cause issues as they are still in caches and might need more wingmen, but it should be less problems from this point. Hopefully this will give the system a chance to catch up.

We have now passed 10 days since the blc35s that were so bad were last sent. I'm assuming there is still a 10 day cache size limit. So hopefully a bunch more of the blc35s have gone through the system. Now we just need to wait for the time out date for these files to finally be done with them.

If they report before the deadline, won't the deadline just trigger the sending of the _2 task and then the deadline for those...........

edit: March 20 for one of the blc35s I still have.

Yes this is the way I would expect it to work. If it is returned before the deadline unless it is returned as "inconclusive" a _2 task will not need be sent out

---

results returned is a bit high at 164,154 per hour... are we getting shorties or bad data??

I'm seeing quite a few groups of resends, many of which are noise bombs.

Edit- and looks like there are a few shorties out and about as well.

---

Grant
Darwin NT

But blc35 was mainly noise bombs so probably will go to at least _2.