Recovery from all of the weekend mishaps continued throughout the evening, and we had our typical Tuesday outage for database backup/etc. today. It went a little long this week as we took care of several extra things: rebooting the science database to make sure we're still not getting those mysterious spurious drive failures, and adding a row to a table in the science database (which required recompilation of several backend executables). As well, we moved several more workunit directories around to balance the load between two of our NAS's.

I've actually been mostly working on science code to do some quick looks at the current multibeam data. Gotta make sure it ain't garbage, you know?

- Matt

---

-- BOINC/SETI@home network/web/science/development person
-- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude

Recovery from all of the weekend mishaps continued throughout the evening, and we had our typical Tuesday outage for database backup/etc. today. It went a little long this week as we took care of several extra things: rebooting the science database to make sure we're still not getting those mysterious spurious drive failures, and adding a row to a table in the science database (which required recompilation of several backend executables). As well, we moved several more workunit directories around to balance the load between two of our NAS's.

I've actually been mostly working on science code to do some quick looks at the current multibeam data. Gotta make sure it ain't garbage, you know?

- Matt

Thanks Again for Posting and Keepin' SETI Users Informed - It is Much Appreciated Sir!

I've actually been mostly working on science code to do some quick looks at the current multibeam data. Gotta make sure it ain't garbage, you know?

Is that why the splitters are off, so you can analyze the MB data before giving more out?

i think if you look at the Current result creation rate 12.00/sec. its still creating work units just not showing that the spliters servers are running on the server page.

les

I've actually been mostly working on science code to do some quick looks at the current multibeam data. Gotta make sure it ain't garbage, you know?

Is that why the splitters are off, so you can analyze the MB data before giving more out?

Looks like we've got a new problem with the status page code. The splitters are running full bore (and slowing other things I'm doing on lando to a crawl.)

Eric

---

@SETIEric@qoto.org (Mastodon)

Actually.. not a problem - just that the status page has been showing the status of the classic splitters, not the multibeam splitters. I just changed that. Have a looksee.

- Matt

---

-- BOINC/SETI@home network/web/science/development person
-- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude

Actually.. not a problem - just that the status page has been showing the status of the classic splitters, not the multibeam splitters. I just changed that. Have a looksee.

- Matt

That's better, but the 3 classic and 12 multibeam splitters still show disabled.

---

Actually.. not a problem - just that the status page has been showing the status of the classic splitters, not the multibeam splitters. I just changed that. Have a looksee.

- Matt

That's better, but the 3 classic and 12 multibeam splitters still show disabled.

In another post, Mat found running all of the splitters caused a slowdown in work unit production. He has tuned the number of splitter under normal load to slowly increase the number of work unites to send.

---

Actually.. not a problem - just that the status page has been showing the status of the classic splitters, not the multibeam splitters. I just changed that. Have a looksee.

- Matt

That's better, but the 3 classic and 12 multibeam splitters still show disabled.

Dena is right....Matt only runs at most 4 splitters, else the filesystem will overload. As long as at least one splitter is running, WU are being generated.

Actually.. not a problem - just that the status page has been showing the status of the classic splitters, not the multibeam splitters. I just changed that. Have a looksee.

- Matt

What will happen to the classic tapes that remain to be split that have already been read in? Will they be split, deleted, or languish around the hard drives taking up space?

What will happen to the classic tapes that remain to be split that have already been read in? Will they be split, deleted, or languish around the hard drives taking up space?

And is there an "easy" way to let us know how much is left to process for the classic enhanced?

---

Don't know where else to post this. I recently updted to 5.10 and now all my statistics are all screwed up. I am subscribed to two projects, but data only show the Seti data and now all of it either. It appears my cross project id is screwed up. How can I fix it?

---

Don't know where else to post this. I recently updted to 5.10 and now all my statistics are all screwed up. I am subscribed to two projects, but data only show the Seti data and now all of it either. It appears my cross project id is screwed up. How can I fix it?

I'm not sure what is the cause of that. I recommend posting your question with some detail on the Q&A forum, under Windows or whatever OS you're running.
http://setiathome.berkeley.edu/forum_help_desk.php