So tomorrow will be Wednesday?

---

So tomorrow will be Wednesday?

Yes. That is exactly how it works now.

---

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

So tomorrow will be Wednesday?

... confirm ...
... if your livingroom is inside a blue telefonbox ;-)

__W__

---

_______________________________________________________________________________

I had to go out and bring the trashcan back from the curb. I saw the maintenance notice and also assumed I had lost a day, didn't register until a couple hours later.........gettin' real old(me).

---

"Sour Grapes make a bitter Whine." <(0)>

Monday must be the new Tuesday.

Weekly Outage and Initial Catch Up
Every Monday morning (Pacific time) we begin a four hour data distribution outage for database and systems maintenance. The upload/download servers will be offline during this time. Afterwards you may experience connectivity issues for several more hours as the servers catch up with demand. 11 Apr 2016, 15:34:47 UTC

Nice of them to give us warning of this change... <snicker>

---

.

Hello, from Albany, CA!...

Not Panic Mode, but SSP does show us new GBT files are now splitted :)

Not Panic Mode, but SSP does show us new GBT files are now splitted :)

Ooh la la....
I do hope the kitties snag a few!
Meow!

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

And which SETI program crunches these new tapes? AP v7 or MB v8 or something else?

---

"Sour Grapes make a bitter Whine." <(0)>

And which SETI program crunches these new tapes? AP v7 or MB v8 or something else?

MB v8 is the one.

If you used the .44 Lunatics installer, you should be good to go.
Meow!

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Thanks Richard and Mark, I'll switch to requesting MB tasks only for a while.

---

"Sour Grapes make a bitter Whine." <(0)>

What an uninformatively filenames! blc3_2bit_guppi_57451_19304_HIP62472_0003 - when it was receieved?

---

What an uninformatively filenames! blc3_2bit_guppi_57451_19304_HIP62472_0003 - when it was receieved?

Eric posted this in the news thread

blc3_2bit_guppi_57451_19304_HIP62472_0003

blc3: Breakthrough Listen
2bit: bits per real sample (4 bit per complex sample)
guppi: File format (Greenbank Ultimate Pulsar Processing Instrument)
57451: Modified Julian Date
19304: Seconds past midnight
HIP62472: Object Name
0003: Observation sequence number

Using the converter here http://www.csgnetwork.com/julianmodifdateconv.html

The date in the example is 03-04-2016 (US) or 04-03-2016 (UK)

The seconds past midnight is about 5.4 hours.

---

The date in the example is 03-04-2016 (US) or 04-03-2016 (UK)

The seconds past midnight is about 5.4 hours.

Auch, I’m get used to DD-MM-YYYY instead MM-DD-YYYY.
Yeah, I’m looking into it, and I see this:

<tape_info>
<name>blc3_2bit_guppi_57451_19958_HIP62472_0005</name>
…
<time_recorded>Fri Mar 4 05:32:38 2016</time_recorded>

---

For those interested

Modified Julian Date, MJD, is a modification of the Julian Date that is routinely used by astronomers, geodesists, scientists, financiers, and even some historians. This dating convention, designed to facilitate simplified chronological calculations, numbers all days in consecutive fashion, beginning at a date sufficiently far into the past so as to precede the historical period. Julian Day Number is an integer counter of the days beginning at noon on January 1, 4713 B.C. (no, even though I may look like it, I was not there...), which is Julian Day Number 0. The Julian Date (as opposed to Julian Day) is the non-integer extension of the Day Number to include a real fraction of day, allowing a continuous time unit. MJD modifies this Julian Date in two ways. The MJD begins at midnight rather than noon (the .5 in the formula), in keeping with more standard conventions and modern representation of time. Secondly, for simplicity, the first two digits of the Julian Date are removed. This is because, for some three centuries following November 17, 1858, the Julian day lies between 2400000 and 2500000. The MJD drops those first "24" digits. Thus, we have as a formula for converting from JD to MJD, MJD = JD - 2400000.5.

---

For those interested

Interesting. Thought I remembered that they had started with a date of 01-01-1970, and counted forward from there. Must have been something different, maybe Unix? Must have been some OS-related function ...

---

For those interested

Interesting. Thought I remembered that they had started with a date of 01-01-1970, and counted forward from there. Must have been something different, maybe Unix?

You are correct, for Unix time started on 01-01-1970

---

For those interested

Interesting. Thought I remembered that they had started with a date of 01-01-1970, and counted forward from there. Must have been something different, maybe Unix? Must have been some OS-related function ...

you're thinking of the linux second count thingy that e.g. BOINC uses to specify a point in time.

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

For those interested

Interesting. Thought I remembered that they had started with a date of 01-01-1970, and counted forward from there. Must have been something different, maybe Unix? Must have been some OS-related function ...

you're thinking of the linux second count thingy that e.g. BOINC uses to specify a point in time.

Yeah, thought it must have been some *ux thing ... thx

---

So, it looks like things are really slow when it comes to purging out (1M) WUs and (2M) Results. The Results pages seems to be running slowly, no surprise given the volume waiting for DB purge ... Wonder what's up?

---