. . @ UnixChick

. . As Jimbocous noted, a new series of tapes have been mounted. BUT! ... it's still the same day ............. :)

. . Why do I feel like it's Groundhog day ... :) (everyday is the 14th October 2018)

Stephen

:)

I wasn't expecting them to add more files !! Very nice! I agree I'm feeling deja vu, but it is good they have enough data to keep us all busy. We have been kicking butt on all the old Aricebo files they have been throwing at us.

I wasn't expecting them to add more files !! Very nice! I agree I'm feeling deja vu, but it is good they have enough data to keep us all busy. We have been kicking butt on all the old Aricebo files they have been throwing at us.

. . Yep chewing 'em up and spitting 'em out ...

Stephen

:)

Not just new tapes, but I'm already getting the first tasks from blc23_2bit_guppi_58405_78644_PSR_J2022+5154_0007

PSR is a Parkes observatory catlog number. That doesn't (by itself) mean that this data was recorded at Parkes - it might be in an overlap area also covered by Green Bank - but it's an interesting straw in the wind.

I'll go and have a look in the datafile header.

Edit - not as exciting as it might have been.

    <data_desc>
      <start_ra>20.38056</start_ra>
      <start_dec>51.9138</start_dec>
      <end_ra>20.380533333333</end_ra>
      <end_dec>51.9139</end_dec>

  <receiver_cfg>
    <name>Green Bank Telescope, Rcvr4_6, Pol 0</name>
    <latitude>38.433121</latitude>
    <longitude>79.839835</longitude>
    <elevation>807.43</elevation>

But interesting. Someone else can work out how close to the Parkes horizon that is, while I go out for lunch.

Just about on the horizon at 22:00 on 2019-03-20
=Altitude = 1.719; azimuth = 5.717
(The effective horizon for the dish is ~1.2deg)

Now if only I could work out when that observation was made it would be possible to give a more accurate location.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Now if only I could work out when that observation was made it would be possible to give a more accurate location.

Happy to oblige.

      <time_recorded>Sun Oct 14 21:50:44 2018</time_recorded>
      <time_recorded_jd>2458406.4102325</time_recorded_jd>

Right, let's re-crunch the numbers.....

Altitude = -74.024
Azimuth = 356.300

We'd better find a TBM for that event.....

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Mind you, the recording time is the Green Bank re-observation. It may take longer to find out when the PSR discovery/cataloging observation run was made.

The best I can do is

apk14: Arumugasamy, P., Pavlov, G. G. & Kargaltsev, O., 2014. XMM-Newton Observations of Young and Energetic Pulsar J2022+3842. ApJ, 790, 103.

aaa+09i: Abdo, A. A., Ackermann, M., Ajello, M., Atwood, W. B., Axelsson, M., Baldini, L., Ballet, J., Barbiellini, G., Baring, M. G., Bastieri, D. & et al., 2009. Fermi Large Area Telescope Detection of Pulsed gamma-rays from the Vela-like Pulsars PSR J1048-5832 and PSR J2229+6114. ApJ, 706, 1331-1340.

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

---

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

A proud member of the OFA (Old Farts Association)

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

Ah - jumping to conclusions again. I must stop doing that.

You can tell I'm a computer, rather than an astronomer.

This is description is from a paper about the observations from the TMRT radio telescope in China. Primary focus was on pulsars emitting heavily at 8.6 Ghz. But the PSR J2022+5154 pulsar emits also at 1.4Ghz, right in the band we listen to for the project at 1421 Mhz (1.4Ghz)

PSR J2022+5154 (B2021+51). PSR J2022+5154 is one of the strongest pulsars at
high frequencies with detections up to 43 GHz (e.g., Kramer et al. 1997a). At low frequencies,
e.g., around 400 MHz, the profile is double-peaked with the trailing component about twice
as strong as the leading one and a component separation of about 8â—¦
(Gould & Lyne 1998).
Around 1.4 GHz, the leading component evidently disappears and the trailing component
bifurcates to two overlapping components.

---

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

A proud member of the OFA (Old Farts Association)

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

Ah - jumping to conclusions again. I must stop doing that.

You can tell I'm a computer, rather than an astronomer.

But jumping to conclusions is GREAT exercise. Ask ANY couch potato :)

---

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

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

:)

At least you are still running a proper Windows version .....

. . Oi!!!

Stephen

:)

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