Heh, tons and tons of Arecibo .VLARs in the "Results ready to send" queue now.
Don't expect many WU's for Nvidia GPU's ....

Edit: Well, except for those 60+ that I just got for my 980 that is :-)

. . I'm hoping the log jam effect of the Arecibo VLAR WUs has been mitigated in some way, call me an optimist :)

Stephen

:)

Heh, tons and tons of Arecibo .VLARs in the "Results ready to send" queue now.

Just curiosity. Where we see that?
AFAIK RTS shows the total SETI@home v8 # avaiable , but not discriminate how many of each flavor.

---

In some of the new Arecibo files, work units (not all, but a few) generated by the splitter code seems to screw up the SoG app - they take forever to run (I have had a few run for upwards of an hour, with remaining time growing; they normally run for 15 minutes or so on my rigs). I noticed it first with 03apr18??, and now with 12dc17aa.

Somehow the WUs generated are incompatible with the app code.

Anyone else notice this? What can be done about it, if I am correct?

---

This needs to be brought to Raistmer's attention. All the aborted tasks took WAY too long to compute. The one thing they have in common is that they have VERY large angle ranges. The highest that I have seen or recall. Over 10 in fact. It's possible that high an angle range is confusing the app by being out of expected compute bounds and it hangs up.

[Edit] Just took a look at my two new aborted tasks that hung up. AR =151. Didn't notice before and that now is the highest angle range I have ever seen. This is likely the reason for the stuck tasks.

---

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

A proud member of the OFA (Old Farts Association)

File deletion backlog continues to grow...

---

Grant
Darwin NT

Thanks for the info Tut. Was not a part of the Beta SoG testing so never have seen these before. If I get another one I will ignore the High Priority running and see if it completes in normal time.

---

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

A proud member of the OFA (Old Farts Association)

Just noticed an AP WU that had been downloading for 30min & was only halfway done. Suspended & re-enabled networking & it finished off at almost 1MB/s (usual download rate is 200-250kB/s).

---

Grant
Darwin NT

Juan, in response to:

Just curiosity. Where we see that?

People glean the information about the nature of tasks being distributed (VLAR/LHAR/Normal) from studying the tasks they receive, it is possible for two people to get an entirely different mix even when their requests for tasks are made within the same time slot.

AFAIK RTS shows the total SETI@home v8 # avaiable , but not discriminate how many of each flavor.

You are right, the Server Stats Page does not discriminate between the source telescope for the "normal" SETI tasks.

---

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

I could fall into a bath tub full of boobs and still end up sucking my thumb, all I see are numbers and letters on each task only time
I know I have something different is when it shows an AP job..Yeah I'm thick :)

Sorry my attempt at humour, noticed threads getting a little tense out there..

LOL. Love your comment as I had never run across that euphemism before.

Pretty simple to determine just what and where tasks originate by the naming convention and the first letters or number in the task name.

BLC (Breakthrough Listen Project) tasks always start with BLC in the name. They are only Multiband tasks. They originate from the Green Bank Telescope in West Virginia.

AP tasks always start with ap in the name. The originate solely from the Arecibo Telescope in Puerto Rico.

Any task starting with just numbers is an Arecibo Multiband task. They originate solely from the Arecibo Telescope.

---

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

A proud member of the OFA (Old Farts Association)

LOL. Love your comment as I had never run across that euphemism before.

Pretty simple to determine just what and where tasks originate by the naming convention and the first letters or number in the task name.

BLC (Breakthrough Listen Project) tasks always start with BLC in the name. They are only Multiband tasks. They originate from the Green Bank Telescope in West Virginia.

AP tasks always start with ap in the name. The originate solely from the Arecibo Telescope in Puerto Rico.

Any task starting with just numbers is an Arecibo Multiband task. They originate solely from the Arecibo Telescope.

. . And the Arecibo tasks are friendly in that the first 6 characters are the file date, as in 12dc17 is the 12th December 2017. The date component in the Blc file names comes later and is a modified Julian date, you will need a date converter to make sense of those but they are readily available on the internet :)

Stephen

:)

Some light relief :-) It's amazing what one comes across when following links.

Employ Cliff to sort out the database :-)

Nice one UCB :-)

Some light relief :-) It's amazing what one comes across when following links.

Employ Cliff to sort out the database :-)

Nice one UCB :-)

. . Maybe we need Cliff to find ET, though he would be further away than Germany ...

Stephen

:)

Thanks Keith and Stephen for explaining it for me :)

I'm guessing the mix of data streams has messed up the flow. The ready to send is high the out in the field has dropped and the results ready to purge from db is at 5 million and still going up.

is this a problem?

I'm guessing the mix of data streams has messed up the flow. The ready to send is high the out in the field has dropped and the results ready to purge from db is at 5 million and still going up.

is this a problem?

The Results-awaiting-purge climbing, along with WU awaiting-deletion aren't a good sign.

And to add to that, for the last 4 hours I've been getting quite a few "Temporarily failed download: transient HTTP error" showing up in my Event logs.

---

Grant
Darwin NT

No problem getting work so far. And no comms issues with the servers. Crossing fingers that holds.

---

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

A proud member of the OFA (Old Farts Association)

No problem getting work so far. And no comms issues with the servers. Crossing fingers that holds.

Yeah, looks like the usual "post about a problem, and it stops" occurred again.

---

Grant
Darwin NT

I think I found a corrupted task file ... blc11_2bit_guppi_58137_42360_HIP64241_0045.2736.818.22.45.145.vlar_6
It seems to be running download errors now.
I'm #7 on the list.
http://setiathome.berkeley.edu/workunit.php?wuid=2865073343

I think I found a corrupted task file ... blc11_2bit_guppi_58137_42360_HIP64241_0045.2736.818.22.45.145.vlar_6
It seems to be running download errors now.
I'm #7 on the list.
http://setiathome.berkeley.edu/workunit.php?wuid=2865073343

blc11 ??

---

Humans may rule the world...but bacteria run it...