I picked up 110 on one machine and have just suspended everything other than AP processing. I'm curious to see what I've actually got. Combo of CPU and Intel and Nvidia GPU(not that it should make a difference if it's a GIGO problem).

Maybe it's a Subversive Plot to generate low AP credits thereby encouraging less 'AP Specializers'(myself included).....":D>

[edit] Well that was like giving my processors a laxative..........flushed the cache at an average of 3 sec a wu. Definitely a data GIGO problem.

---

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

One box had 74 and 1 wasn't totally blanked, it got 592 credits another box got 25 all totally blanked, the 3rd box hasn't started on it's 44. The up side is you don't waste much time on this garbage.

---

One box had 74 and 1 wasn't totally blanked, it got 592 credits another box got 25 all totally blanked, the 3rd box hasn't started on it's 44. The up side is you don't waste much time on this garbage.

Just a lot of bandwidth...

Has anybody applied the compressibility test to the datafiles, to find put if it's just an extreme version of the B3_P1 problem?

here is an ap b3_p1 if you would like to try it

here is an ap b3_p1 if you would like to try it

Well, that 8,196 KB file compresses to 4,427 KB (Windows implementation of ZIP algorithm) or 4,088 KB (7-zip). Those values are indicative of the 'stuck bit' error which has plagued us for many years - believed to be a fault in the digital recording system at Arecibo, and not indicative of radar contamination at all. The question is - how many of the 13 other channels (7 beams, 2 polarisations of each beam) are suffering from the same problem? Intact 8-bit recordings should be barely compressible at all.

For frosting on the cake the remaining 44 were 100% blanked. Taking a closer look at the one that wasn't blanked LOL it was a resend originally created 24 Aug 2016.

---

For frosting on the cake the remaining 44 were 100% blanked. Taking a closer look at the one that wasn't blanked LOL it was a resend originally created 24 Aug 2016.

That was probably one of mine originally as that was the date I abandoned a whole bunch because Windows updated and the drivers reverted.....

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

I checked, it wasn't one of yours but if you have any to spare I would gladly take some.

---

Hey, a couple tapes got loaded, and they're actually producing real WUs. Apparently it's been a run for a few hours. It's 430am and I just noticed I have 4 in my cache and they've been crunching for about 3 hours.

I'll see if I can get a few more before this run ends. It looks like there's only one tape left to split and it doesn't take long when there are 4 splitters working on one tape.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

Did anyone ever work out whether the 2016 tapes were 'radar_blanked' or 'bit_stuck'?

I managed to snag 9 out of that run, what is usable remains to be seen....

---

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

Did anyone ever work out whether the 2016 tapes were 'radar_blanked' or 'bit_stuck'?

Stderr says 100% blanked. I do not know if that is accurate or not.
See: http://setiathome.berkeley.edu/result.php?resultid=5134438797

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

Did anyone ever work out whether the 2016 tapes were 'radar_blanked' or 'bit_stuck'?

Stderr says 100% blanked. I do not know if that is accurate or not.
See: http://setiathome.berkeley.edu/result.php?resultid=5134438797

Stderr says the same thing, whether the task is blanked or the data bit is stuck. That's why I asked people to apply the compression test (some way down this thread, by now) - but that can only be done while the tasks are cached on your machines, or (for a very short time) in progress. By the time you can read stderr, it's too late.

Stderr says the same thing, whether the task is blanked or the data bit is stuck. That's why I asked people to apply the compression test (some way down this thread, by now) - but that can only be done while the tasks are cached on your machines, or (for a very short time) in progress. By the time you can read stderr, it's too late.

Understood

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

It looks like the recent mini run was not totally radar blanked, as Captain Obvious I deem that to be a good thing.

---

It looks like the recent mini run was not totally radar blanked, as Captain Obvious I deem that to be a good thing.

By that, do you mean the recent block of tasks from 2009 tapes, such as the ones that the MB splitters are still working through?

If so, it still doesn't allay my fears of a possible antenna or recorder problem rendering all tapes from 2016 as useless for Astropulse.

Well it does eliminate server problems doesn't it?

---

That's what I was thinking. They were, indeed, 2009 tapes, and they produced usable WUs, which I believe eliminates a problem with the splitters.

Pretty sure that just means that the 2016 tapes have something wrong with them if APs are 100% blanked for every channel and every WU. Figuring out what the problem is.. is a whole other can of worms. Is it the receiver? Is it the recording hardware?

I thought I remembered reading Matt explain a long while back that one of the channels was used solely to say when radar was happening, so that channel could be used as an overlay to all the others for blanking. Could it be that channel has glitched-out, or was there a slight tweak/format change in how the data is written to disk, and that is what's making all channels useless when the tape goes through the RFI cleaner before being loaded as a tape to split?

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

I was wondering if anybody can help me with this I have not changed anything for several months since I installed Lunatics. I don't know much about computers so any help would be appreciated thanks
I got this in my notice section of my bionic
SETI@home: Notice from server
Unknown app name setiathome_v7 in app_info.xml
9/13/2016 8:26:38 PM
This is in my log file
9/13/2016 8:39:03 PM | SETI@home | Message from server: Unknown app name setiathome_v7 in app_info.xml
This is my cc config file

<cc_config>
<log_flags>
<file_xfer>1</file_xfer>
<sched_ops>1</sched_ops>
<task>1</task>
<android_debug>0</android_debug>
<app_msg_receive>0</app_msg_receive>
<app_msg_send>0</app_msg_send>
<async_file_debug>0</async_file_debug>
<benchmark_debug>0</benchmark_debug>
<checkpoint_debug>0</checkpoint_debug>
<coproc_debug>0</coproc_debug>
<cpu_sched>0</cpu_sched>
<cpu_sched_debug>0</cpu_sched_debug>
<cpu_sched_status>0</cpu_sched_status>
<dcf_debug>0</dcf_debug>
<disk_usage_debug>0</disk_usage_debug>
<file_xfer_debug>0</file_xfer_debug>
<gui_rpc_debug>0</gui_rpc_debug>
<heartbeat_debug>0</heartbeat_debug>
<http_debug>0</http_debug>
<http_xfer_debug>0</http_xfer_debug>
<mem_usage_debug>0</mem_usage_debug>
<network_status_debug>0</network_status_debug>
<notice_debug>0</notice_debug>
<poll_debug>0</poll_debug>
<priority_debug>0</priority_debug>
<proxy_debug>0</proxy_debug>
<rr_simulation>0</rr_simulation>
<rrsim_detail>0</rrsim_detail>
<sched_op_debug>0</sched_op_debug>
<scrsave_debug>0</scrsave_debug>
<slot_debug>0</slot_debug>
<state_debug>0</state_debug>
<statefile_debug>0</statefile_debug>
<suspend_debug>0</suspend_debug>
<task_debug>0</task_debug>
<time_debug>0</time_debug>
<trickle_debug>0</trickle_debug>
<unparsed_xml>0</unparsed_xml>
<work_fetch_debug>0</work_fetch_debug>
</log_flags>
<options>
<abort_jobs_on_exit>0</abort_jobs_on_exit>
<allow_multiple_clients>0</allow_multiple_clients>
<allow_remote_gui_rpc>0</allow_remote_gui_rpc>
<client_version_check_url>http://boinc.berkeley.edu/download.php?xml=1</client_version_check_url>
<client_new_version_text></client_new_version_text>
<client_download_url>http://boinc.berkeley.edu/download.php</client_download_url>
<disallow_attach>0</disallow_attach>
<dont_check_file_sizes>0</dont_check_file_sizes>
<dont_contact_ref_site>0</dont_contact_ref_site>
<dont_use_vbox>0</dont_use_vbox>
<exit_after_finish>0</exit_after_finish>
<exit_before_start>0</exit_before_start>
<exit_when_idle>0</exit_when_idle>
<fetch_minimal_work>0</fetch_minimal_work>
<fetch_on_update>0</fetch_on_update>
<force_auth>default</force_auth>
<http_1_0>0</http_1_0>
<http_transfer_timeout>300</http_transfer_timeout>
<http_transfer_timeout_bps>10</http_transfer_timeout_bps>
<max_event_log_lines>2000</max_event_log_lines>
<max_file_xfers>8</max_file_xfers>
<max_file_xfers_per_project>2</max_file_xfers_per_project>
<max_stderr_file_size>0</max_stderr_file_size>
<max_stdout_file_size>0</max_stdout_file_size>
<max_tasks_reported>0</max_tasks_reported>
<ncpus>-1</ncpus>
<network_test_url>http://www.google.com/</network_test_url>
<no_alt_platform>0</no_alt_platform>
<no_gpus>0</no_gpus>
<no_info_fetch>0</no_info_fetch>
<no_priority_change>0</no_priority_change>
<os_random_only>0</os_random_only>
<proxy_info>
<socks_server_name></socks_server_name>
<socks_server_port>80</socks_server_port>
<http_server_name></http_server_name>
<http_server_port>80</http_server_port>
<socks5_user_name></socks5_user_name>
<socks5_user_passwd></socks5_user_passwd>
<http_user_name></http_user_name>
<http_user_passwd></http_user_passwd>
<no_proxy></no_proxy>
</proxy_info>
<rec_half_life_days>10.000000</rec_half_life_days>
<report_results_immediately>0</report_results_immediately>
<run_apps_manually>0</run_apps_manually>
<save_stats_days>30</save_stats_days>
<skip_cpu_benchmarks>0</skip_cpu_benchmarks>
<simple_gui_only>0</simple_gui_only>
<start_delay>0.000000</start_delay>
<stderr_head>0</stderr_head>
<suppress_net_info>0</suppress_net_info>
<unsigned_apps_ok>0</unsigned_apps_ok>
<use_all_gpus>0</use_all_gpus>
<use_certs>0</use_certs>
<use_certs_only>0</use_certs_only>
<vbox_window>0</vbox_window>
</options>
</cc_config>

---

I was wondering if anybody can help me with this I have not changed anything for several months since I installed Lunatics. I don't know much about computers so any help would be appreciated thanks
I got this in my notice section of my bionic
SETI@home: Notice from server
Unknown app name setiathome_v7 in app_info.xml
9/13/2016 8:26:38 PM
This is in my log file
9/13/2016 8:39:03 PM | SETI@home | Message from server: Unknown app name setiathome_v7 in app_info.xml
This is my cc config file

<cc_config>
...
</cc_config>

Hi, cc_config won't help you here, the issue is in your app_info.xml file, located in the ... BOINC\projects\setiathome.berkeley.edu directory.
Look for a section starting
<app>
<name>setiathome_v7</name>
and get rid of all <app> and <app_version> segments that refer to <app_name>setiathome_v7</app_name>.

Be very careful not to get confused with <app_name>astropulse_v7</app_name>, it's easy to do.

Or, for a better time, run the Lunatics 0.44 installer, which will rewrite all this stuff.

Later, Jim ...

---