I don't think the origin is from the Parkes Telescope. PSR is just the normal catalog identifier for a pulsar. We have crunched many pulsar data sets.

If the origin or data source was Parkes the catalog number should be a PKS identifier. http://cds.u-strasbg.fr/cgi-bin/Dic-Simbad?PKS

. . Thanks for the reference Keith, but I think I can see the confusion ...

PKS (Parkes obs.)= (P) = (PSR)

. . But as you say PSR (in this case) would probably refer to the pulsar ...

Stephen

:)

Astronomical objects are classified by their type and catalog number. PSR is the standard designation for pulsars. But in the past PSR was also referenced as Parkes Survey Region but was deprecated in favor of PSK because of the confusion with the standard classification for pulsars. Easily confused. The target PSR_J2022+5154 was listed as a northern hemisphere object and so probably not observable from Parkes.

The RA (Right Ascension) and DEC (Declination) is how celestial objects are located. Equivalent to LAT and LONG except for the celestial sphere. The PSR_J2022+5154 object is located just between the constellation Cepheus and the constellation Cygnus in the northern hemisphere http://www.avastronomyclub.org/skymap/d/skymap.php

A list of the common astronomical catalogues is here. https://en.wikipedia.org/wiki/List_of_astronomical_catalogues We've had targets from Messier, NGC, Hipparchos, 3C, Gliese, Kepler, 2MASS and a few more I can't remember.

---

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

A proud member of the OFA (Old Farts Association)

No Panic , just curiosity.

Results received in last hour ** 0 1,478 146,664

The results received in the last hour is higher than our usual 120k. It is surprising to me that the number is higher than usual even with the high amount of AP results returned as well. Are we getting garbage WUs right now? or have more fast machines joined the cause?? I'm really happy that the seti system seems to be handling things well and that the replica is also keeping up.

I would say there have been a fair increase of early overflows in all the old Arecibo data we've been crunching. Also I would say there has been an increase in faster hosts because of additional volunteers running the special app on Linux.

---

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

A proud member of the OFA (Old Farts Association)

Also a lot of VHAR 'shorter by design'.

It appears the BUG affecting the Credits has struck again. Not long ago it gave an extra 1 million RAC & 1 BILLION Credits to Juan after a system rebuild. Before then Juan and Petri were very close for the #1 spot on the SETI all time list. The 1 Million extra RAC has finally worked down to normal, however, the 1 Billion extra credits is still there. Juan and Petri were close with Petri at #1, now look at it, https://stats.free-dc.org/stats.php?page=hosts&proj=sah&offset=1 Take away that extra One Billion credits and they would still be close, but, I don't see how Petri could be lower considering his RAC.

Now we have a new Bug. Some Host Appeared on the front page overnight that wasn't there yesterday, this one, https://setiathome.berkeley.edu/show_host_detail.php?hostid=8690734 Sorry, that machine shouldn't be there. Looking down a ways to #28, you see where it probably was, until the Bug, https://setiathome.berkeley.edu/show_host_detail.php?hostid=8682108

Owner 	Anonymous
Created 	7 Mar 2019, 13:28:22 UTC
Total credit 	0
Average credit 	0.00
CPU type 	GenuineIntel
Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz [Family 6 Model 60 Stepping 3]
Number of processors 	8
Coprocessors 	NVIDIA GeForce GTX 1060 6GB (4095MB) driver: 418.43 OpenCL: 1.2
Virtualization 	None
Operating System 	Linux Ubuntu
Ubuntu 18.04.2 LTS [4.15.0-46-generic]

I'm not sure what the BUG is, but, giving out an Extra One Billion in Credit is not nice. There are probably other instances that have been overlooked, the one that happened overnight may be just the tip.

I mentioned Juan’s host bug a while back. But I’m not sure who would have the ability to “fix” such a bug. My theory was that something is happening host-side to affect the change on the server, but general consensus from some others seemed to be that it shouldn’t be possible for that to happen. But it did coincide with Juan’s system crash, I really don’t know *shrug*

But I don’t think those two systems are the same. One lists Magne as the owner, the other Anonymous. As far as I know you can’t hide your hosts a la carte. It’s all or nothing.

One thing seems certain. The bug only affects host stats. But not overall user stats. So at least the user/participant leaderboard stays fair. For now.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

Try looking at who #28 is listed as belonging to, https://setiathome.berkeley.edu/top_hosts.php?sort_by=expavg_credit&offset=20
ID: 8682108
#28 Magne 171,989.52 8,889,326 7.8.3
GenuineIntel Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz [Family 6 Model 60 Stepping 3] (8 processors)
NVIDIA GeForce GTX 1060 6GB (4095MB) driver: 418.43 OpenCL: 1.2
Linux Ubuntu Ubuntu 18.04.2 LTS [4.15.0-46-generic]

Now look at #8, https://setiathome.berkeley.edu/top_hosts.php
ID: 8690734
#8 Magne 363,269.95 18,080,802 7.4.44
GenuineIntel Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz [Family 6 Model 60 Stepping 3] (8 processors)
[5] NVIDIA GeForce GTX 1060 6GB (4095MB) driver: 418.43
Linux 4.15.0-46-generic

Now note Magne only has One Linux Machine, https://setiathome.berkeley.edu/hosts_user.php?userid=118177
You should also note the RAC on his User page, Recent average credit 199,322.93
Most people would conclude it is the SAME machine.

You can also look at Juan's page and note the Credit; https://setiathome.berkeley.edu/show_user.php?userid=8606388
Total credit: 450,616,983
But when you look at his host, https://setiathome.berkeley.edu/hosts_user.php?userid=8606388
ID: 8662921: Total credit: 1,375,790,492
So, how does a Total of 450,616k translate to a Host of 1,375,790k?
Strange things around here...

Results received in last hour ** 0 1,478 146,664

The results received in the last hour is higher than our usual 120k. It is surprising to me that the number is higher than usual even with the high amount of AP results returned as well. Are we getting garbage WUs right now? or have more fast machines joined the cause?? I'm really happy that the seti system seems to be handling things well and that the replica is also keeping up.

. . I have had some large numbers of noise bombs so I am guessing it is the former ...

Stephen

<shrug>

Ah I see now. I had only clicked the links you provided and they showed different Owners.

But since stats on the second page haven’t updated yet that’s why it’s still there. (And shows anonymous when you actually click on it from the second page)

The anonymous setting must be what happens when a host gets deleted. I believe when this happened to Juan also, it deleted his old host too. I’m aware of the contradiction between Juan’s host and user stats. I posted about that some time ago in another thread.

Edit: found the old post where it was discussed previously.

https://setiathome.berkeley.edu/forum_thread.php?id=83833&postid=1978139#1978139

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

. . Aaahh! Here we go again, 24 hours (or so) to maintenance outage and the uploads are playing up .... :(

Stephen

:(

. . Aaahh! Here we go again, 24 hours (or so) to maintenance outage and the uploads are playing up .... :(

Stephen

:(

Just like a switch was flipped ...

---

. . Aaahh! Here we go again, 24 hours (or so) to maintenance outage and the uploads are playing up .... :(

Stephen

:(

Just like a switch was flipped ...

Mon 25 Mar 2019 08:32:57 AM CDT | SETI@home | Temporarily failed upload of blc23_2bit_guppi_58405_84300_HIP86137_0023.13785.818.21.44.234.vlar_0_r1167924088_0: transient HTTP error

Or maybe it is a "Friday issue". The servers get "congested" right before maintenance?

Tom

---

A proud member of the OFA (Old Farts Association).

Hopeful that the elves in the lab notice the upload server is acting up and fix it today when they get in.

---

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

A proud member of the OFA (Old Farts Association)

For those of you who never bother to ask yourselves which transient error:

25/03/2019 14:17:58 | SETI@home | [http] [ID#3033] Info:  Failed to connect to setiboincdata.ssl.berkeley.edu port 80: Timed out

That's one we can't do anything about - don't mess with any files.

Up loads have started working again but it is a painful process.

---

i can mostly stay on top of my uploads on the 2 slower machines, but the beast is just too fast. uploads go slower than the machine can process the WUs. the the pending uploads is just growing and growing. this is with max file transfers set to it's max of 8.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

It would be nice if someone could pop the clutch, lots of timeouts here, on average I'm 15 behind on uploads, if I push it, about 1-4.86Kb sec for uploads, reporting seems stalled.

---

Savoir-Faire is everywhere!
The T1 Trust, T1 Class 4-4-4-4 #5550, America's First HST

I'm also getting a lot of my uploads stuck at 100% while others timeout and just go into retry loops.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

PANIC! The ready to send queue is low, and people are having time out issues for a while, something is wrong!!

Can we tell if it is a Berkeley connection issue or a seti one?? is it a problem with the upload machine??

Time for someone to check the cables or kick the machine.

PANIC! The ready to send queue is low, and people are having time out issues for a while, something is wrong!!

Can we tell if it is a Berkeley connection issue or a seti one?? is it a problem with the upload machine??

Time for someone to check the cables or kick the machine.

Richard, already posted the issue is with the upload server.

25/03/2019 14:17:58 | SETI@home | [http] [ID#3033] Info: Failed to connect to setiboincdata.ssl.berkeley.edu port 80: Timed out

---

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

A proud member of the OFA (Old Farts Association)