On Sunday, May 17th campus is upgrading the network infrastructure at the facility hosting our servers. We will bringing the projects down for about 6-8 hours (starting at 8am, Pacific Time) to avoid complications during the upgrade.

---

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

NOTE: this upgrade is largely to allow 10-gigabit connections between machines throughout the data center, which will speed up various campus services, but do nothing to speed up SETI@home traffic, or grant us more bandwidth. Nevertheless, as our servers are part of the data center, we are affected by the upgrade.

- 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

Thanks for the heads up Matt.

---

Thanks for that Matt.

Claggy

Thinking ... Matt Eric David etc. should all be around for the maintenance to chit chat with the IT team ... You never know you might pickup a good volunteer, or even give you a 14th opinion on databases. :)

---

On Sunday, May 17th campus is upgrading the network infrastructure at the facility hosting our servers. We will bringing the projects down for about 6-8 hours (starting at 8am, Pacific Time) to avoid complications during the upgrade.

http://setiathome.berkeley.edu/utc.php

8am PT, is -8 hrs UTC.

This means 16:00 UTC to 24:00 UTC (8 hrs) - right?

This would mean: 17. Sunday 18:00 to 18. Monday 02:00 (MiddleEuropeanSummerTime)

---

...
http://setiathome.berkeley.edu/utc.php

8am PT, is -8 hrs UTC.
...

No, Berkeley is on Pacific Daylight Time, UTC -7.

                                                                   Joe

Thanks.

This means 15:00 UTC to 23:00 UTC (8 hrs).

This would mean: 17. Sunday 17:00 to 18. Monday 01:00 (MiddleEuropeanSummerTime)

---

Expect the unexpected - an FYI - headsup
NASA Spaceweather.com News: 2 items -- coinciding with "our" Network update

GLANCING BLOW ON MAY 17: NOAA forecasters estimate a 45% chance of polar geomagnetic storms on May 17th when a CME is expected to deliver a glancing blow to Earth's magnetic field. The storm cloud was hurled in our direction by a magnetic filament, which erupted away from the sun on May 13th
=
Coronal Holes: 15 May 15
A stream of solar wind flowing from the indicated coronal hole should reach Earth on May 18-19. Credit: SDO/AIA.
=
Anytime either of these type events occur, otherwise unexplained phenomena tag along ie geo-magnetically influenced phenomena; like cell phones / Wi-Fi and other radio wave/microwave stuff, TV signals and internet connectivity often affected. Usually temporarily but noticeable.

I would venture to say, it's possible that even Arecibo et al recordings could be affected ( by severe "noise" and interference during these events ).

---

well, that's about it... see you on the other side folks. Hope the project recovers quickly after the outage with no AP's to keep the cores busy ;-)

---

Yup...
Hope the IT people at the colo have all their ducks in a row and it goes smoothly for them and Seti.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Expect the unexpected - an FYI - headsup
NASA Spaceweather.com News: 2 items -- coinciding with "our" Network update

GLANCING BLOW ON MAY 17: NOAA forecasters estimate a 45% chance of polar geomagnetic storms on May 17th when a CME is expected to deliver a glancing blow to Earth's magnetic field. The storm cloud was hurled in our direction by a magnetic filament, which erupted away from the sun on May 13th
=
Coronal Holes: 15 May 15
A stream of solar wind flowing from the indicated coronal hole should reach Earth on May 18-19. Credit: SDO/AIA.
=
Anytime either of these type events occur, otherwise unexplained phenomena tag along ie geo-magnetically influenced phenomena; like cell phones / Wi-Fi and other radio wave/microwave stuff, TV signals and internet connectivity often affected. Usually temporarily but noticeable.

I would venture to say, it's possible that even Arecibo et al recordings could be affected ( by severe "noise" and interference during these events ).

You can always check the Arecibo Observatory Schedule to see if anyone is using the telescope for something that would allow SETI@home to record data.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

You can always check the Arecibo Observatory Schedule to see if anyone is using the telescope for something that would allow SETI@home to record data.

Good to see that Jill Tarter still has a couple of SETI projects on the schedule.

---

"It is often darkest just before it turns completely black."

Thanks HAL - actually just planting "seed"
Re: Pre and Post Debunking/Troubleshooting potentially "Bad" data from tapes/images; possibly correlating to these highly-magnetic events.
=
My thoughts are, to correlate "significant events such as Xclass Solar Flares and CMEs or EMPs or significant Solar winds" Calendar with Recordings Dates and Times, in order to cull these from our precious Time and Efforts.

Or, build-in a specific algorithm or filter(s) to try and salvage the potentially compromised data from these correlated recordings.

---

From the traffic graphs during this outage, I tend to believe BOINC handles the outages better than the STEI servers.

One might want to consider literally "pulling the plug" (internet wise) during maintenance periods.

---

Thanks HAL - actually just planting "seed"
Re: Pre and Post Debunking/Troubleshooting potentially "Bad" data from tapes/images; possibly correlating to these highly-magnetic events.
=
My thoughts are, to correlate "significant events such as Xclass Solar Flares and CMEs or EMPs or significant Solar winds" Calendar with Recordings Dates and Times, in order to cull these from our precious Time and Efforts.

Or, build-in a specific algorithm or filter(s) to try and salvage the potentially compromised data from these correlated recordings.

I would guess that they would shutdown activity at Arecibo if to much interference would be caused by an event. It would be interesting to see if any data we have processed correlates with any specific events & what the outcome of the data we have processed happens to be.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

@HAL: It would be interesting to see if any data we have processed correlates with any specific events & what the outcome of the data we have processed happens to be.
=
Precisely my thoughts/hypothesis.
I would postulate, event logs are available @ spaceweather.com or elsewhere among NASA archives, defining the vectors, azimuth or other such geo-locations of potentially harmful events with respect to Arecibo and other radio telescopes (and their recordings).
Certainly possible as well, that Southern-located telescopes aren't *as affected due to the nature of the magnetosphere - and whether or not they are facing toward these blasts when they arrive ( as opposed to being on opposite side of Earth at the time)
Dunno, after reading the post about data corruption due to an employee opening a microwave prematurely....sheesh.
Reminds me of losing data on floppy media when my mobile phone rang next to it or using a refrig magnet to hold one on a filing cabinet....and lose your Report
=
Does seem plausible to view dated results (specifically invalids) and match up with geo-magnetic event calendars....to see if a Batch could be affected.

---

Ya Brent, thought about that. But my RAC already affected it seems during these Outages and slow recovery. Pending bucket goes nutz and seems to take 2 months to clear half of those things anyway- I've *still got some in there from Feb and March. Beats me what the holdup is.

Just lost my 1% badge after the back to back outages last week - RAC dropped below 15k I guess, was 16+ now just 14.7
Of course my AP drought here is another factor - dunno why they've been so scarce. I hear some are getting dozens-100's....no logic in it.
[sigh]

---