Posts by [SETI.Germany] Sutaru Tsureku (aka Dirk :-)

1) Message boards : Politics : Greatest Best Leader of ALL TIME Yep Dat BeeeZZZ Big BIg BIG Hands Golden Haired Long Black Coat Wearin; WINNING ALWAYS Prez #45 45ers Gots His Back. You, Not So Much.......Yap (Message 1939243)
Posted 12 Jun 2018 by Profile [SETI.Germany] Sutaru Tsureku (aka Dirk :-)
Post:
Thanks to you both.

Clyde wrote:
(...)
Seti@home is an International Effort of resources headquartered in a very liberal (Anti-Trump) California University.
(...)

Maybe I could read somewhere an officially statement of the California University about this?
2) Message boards : Number crunching : (SOLVED: 'normal' .vlar WUs to AMD GPUs now?) - NEW: So much 'ghost' WUs? (Message 1939138)
Posted 11 Jun 2018 by Profile [SETI.Germany] Sutaru Tsureku (aka Dirk :-)
Post:
Message boards : Politics : D. Trump president of the USA - Why I should still support SETI@home?

- - - - - - - - - -

A moderator moved my message to an old thread: Message 1939137.
I'll get in contact with him and ask if he will reopen my.
3) Message boards : Politics : Greatest Best Leader of ALL TIME Yep Dat BeeeZZZ Big BIg BIG Hands Golden Haired Long Black Coat Wearin; WINNING ALWAYS Prez #45 45ers Gots His Back. You, Not So Much.......Yap (Message 1939137)
Posted 11 Jun 2018 by Profile [SETI.Germany] Sutaru Tsureku (aka Dirk :-)
Post:
I don't want to offend anyone.


I don't know if I could/should still support the US BOINC project SETI@home.


I would like to understand the US citizen.


~ 50.x % of the US citizen elected D. Trump.
They have the same opinion as him?
Or they don't wanted Hillary Clinton as president?

~ 50.x % of the US citizen still have the same opinion as D. Trump?


I don't need to repeat all the things that D. Trump made.
He want to destroy the world?
The last, punitive tariffs for non-US steel and aluminum.
The EU will answer with punitive tariffs to Harley-Davidson, peanut butter, Whiskey...
D. Trump answer with punitive tariffs for german cars...
The EU answer with...

All the US citizen still have the same opinion as D. Trump?


It looks like the US citizen just like each other. No other outside the US borders.

I ask me, why I should still support an US BOINC project like SETI@home with my german money (hardware and electricity bill)?


Thanks.


[these are just my impressions]
4) Message boards : Number crunching : (SOLVED: 'normal' .vlar WUs to AMD GPUs now?) - NEW: So much 'ghost' WUs? (Message 1938664)
Posted 8 Jun 2018 by Profile [SETI.Germany] Sutaru Tsureku (aka Dirk :-)
Post:
I was in contact with the admins and now it's again like it should...

If you detach/attach SETI in BOINC the PC keep the host ID - no new host ID will created.

BTW, if you want a new host ID: Message 1919418

- - - - - - - - - -

BTW, I decided to stop the support to SETI...


Donald Trump - president of the USA?
I'm speechless.
Enough is enough. (May/2018)
Why should I support an american BOINC project with my german money (hardware and electricity bill)?
If the USA have an other president, maybe I'll think about to come back here.
In the meantime I support the german BOINC project Einstein@Home!
It's a pity. I'm sad. After so many years I supported SETI@home...
I wish you all success and good luck here.
Cheerio!



5) Message boards : Number crunching : (SOLVED: 'normal' .vlar WUs to AMD GPUs now?) - NEW: So much 'ghost' WUs? (Message 1936560)
Posted 21 May 2018 by Profile [SETI.Germany] Sutaru Tsureku (aka Dirk :-)
Post:
Thanks.


I'm stupid... ;-)
I looked to the online overview and saw that the 1st WU in progress is from 3 Apr 2018, 3:28:40 UTC.
So this is the old WU cache before I switched off the machine.

But, before I switched off the machine, I detached/attached SETI in BOINC.
Normally then the status of all WUs in progress will be changed to (something like) 'given up'.

This time this didn't worked.
BOINC got a new host ID from the SETI server.

How can I 'delete' this 'ghost' WUs, if when I detach/attach the SETI server will give a new host ID, instead of to 'give up' the WU cache/s?
6) Message boards : Number crunching : (SOLVED: 'normal' .vlar WUs to AMD GPUs now?) - NEW: So much 'ghost' WUs? (Message 1936535)
Posted 21 May 2018 by Profile [SETI.Germany] Sutaru Tsureku (aka Dirk :-)
Post:
I searched but didn't found anything about this ''normal' .vlar WUs to GPUs'.
Please could someone give me an URL?

- - - - - - - - - -

I have just Windows Defender - nothing specially adjusted, default settings.

This 'dual Xeon + quad FuryX' machine didn't had 'ghost' WUs before the break.

The only thing that changed, is that this machine use also both now, DSL + LTE/4G path.
The smaller machine J1900 + GT730 use both paths since months - and no 'ghost' WUs.

To explain...
I live in a small village and have just DSL2000RAM (0.5 MBit/s UL + 1.5-1.9 MBit/s DL).
I'm a Telekom ISP customer and have the Speedport Hybrid router.
If the DSL path is saturated the router send/receive the data also over LTE/4G.
Over LTE/4G additional up to 2.4 MBit/s UL + up to 16 MBit/s DL.
(currently altogether just ~ 1 MBit/s UL + ~ 6 MBit/s DL, bad connection)

Maybe the .xml file of the bigger machine is so much bigger than of the smaller machine that some infos are gone lost on the way to Berkeley?


My machine is the only one which have so much 'ghost' WUs?


EDIT of the title.


[EDIT#2: Currently 793 WUs in progress, this means 393 'ghost' WUs.]
7) Message boards : Number crunching : (SOLVED: 'normal' .vlar WUs to AMD GPUs now?) - NEW: So much 'ghost' WUs? (Message 1936526)
Posted 21 May 2018 by Profile [SETI.Germany] Sutaru Tsureku (aka Dirk :-)
Post:
Is there something 'bigger' wrong?

In the online overview are nearly 800 MB WUs in progress...

But in BOINC are just </= 400 MB WUs (limit of tasks in progress)...

Strange - so many 'ghost' WUs?
8) Message boards : Number crunching : (SOLVED: 'normal' .vlar WUs to AMD GPUs now?) - NEW: So much 'ghost' WUs? (Message 1936525)
Posted 21 May 2018 by Profile [SETI.Germany] Sutaru Tsureku (aka Dirk :-)
Post:
Hello

My quad FuryX machine get since Monday 05/21. 09:54 UTC 'normal' .vlar WUs for the AMD GPUs... - AFAIK they are only for CPUs...
(not the *guppi* .vlar WUs ;-)

Is there something wrong - or the admins decided to send them now to AMD GPUs also?

Thanks


[EDIT: (BTW, after ~ 5 weeks break I switched on again the above mentioned PC yesterday)]
9) Message boards : Number crunching : Asteroids@home website have https proplems? (Message 1919424)
Posted 17 Feb 2018 by Profile [SETI.Germany] Sutaru Tsureku (aka Dirk :-)
Post:
If I click Your account (Asteroids@home) there, I get the above mentioned warning...

;-)
10) Message boards : Number crunching : Asteroids@home website have https proplems? (Message 1919421)
Posted 17 Feb 2018 by Profile [SETI.Germany] Sutaru Tsureku (aka Dirk :-)
Post:
Hello,

since a short time I can't longer log in to my account at Asteroids@home.
Firefox say (german):
Diese Verbindung ist nicht sicher
Der Inhaber von asteroidsathome.net hat die Website nicht richtig konfiguriert. Firefox hat keine Verbindung mit dieser Website aufgebaut, um Ihre Informationen vor Diebstahl zu sch├╝tzen.


Google say:
This connection is not secure
The owner of asteroidsathome.net did not properly configure the site. Firefox has not affiliated with this site to protect your information from theft.


I sent the admin Kyong over the SETI page a private message about this problem, I don't kow if he get a notification about.

Maybe someone can log in at Asteroids@home (maybe with IE or other browser) and can write a private message to Kyong there. In past I did it and got very fast reaction. I guess there he get a notification.

Thanks
11) Message boards : Number crunching : How to get back the old host ID? (Message 1919418)
Posted 17 Feb 2018 by Profile [SETI.Germany] Sutaru Tsureku (aka Dirk :-)
Post:
Thanks to all.

juan BFP, with your explanation I understood it! :-)

Maybe someone could get in contact with the boinc.mundayweb.com/wiki guys and ask if they could make it 'better' (more understandable for the poor english speaking guys ;-)?

Maybe like this (?):

  • Make sure you have no tasks in your queue (Finish & Upload, abort, report them all)
  • Go to the web site of the project, your list of computers and find your old Host ID number and how often BOINC connected the project server (on the bottom of the computer information overview).
  • Stop and Close BOINC.
  • Edit client_state.xml, find the <hostid> tags and replace the number here with the old ID.
  • A few lines above find the <rpc_seqno> tag and insert here the number how much times the computer connected the project server with added 1.
  • Save client_state.xml
  • Restart BOINC.



This way I would had understood it... ;-)



BTW. If someone would like to have a new host ID - no project tasks in BOINC...


  • Stop and Close BOINC.
  • Edit client_state.xml, find the <hostid> tags and add 1 to this number.
  • Save client_state.xml
  • Project update and the project server create a new host ID.



:-)

12) Message boards : Number crunching : How to get back the old host ID? (Message 1919049)
Posted 15 Feb 2018 by Profile [SETI.Germany] Sutaru Tsureku (aka Dirk :-)
Post:
I know my english is poor... ;-)
But I thought I did it correct.

I took the old host ID and wrote it in the <hostid> line.
A few lines above is the <rpc_seqno> line, IIRC there was 250, so I added 1, so I wrote there 251.
Save.
Restart of BOINC, 'SETI project update' and the SETI server gave a new host ID - the old one isn't used.

What I make wrong? *confused*

Thanks
13) Message boards : Number crunching : How to get back the old host ID? (Message 1918982)
Posted 15 Feb 2018 by Profile [SETI.Germany] Sutaru Tsureku (aka Dirk :-)
Post:
Hm, I thought I found the answer on my own, but - it didn't worked...

Here is the trick: How to revert to an older HostID number?

It's because of the newer BOINC Version, or why it don't work anymore?

Thanks
14) Message boards : Number crunching : How to get back the old host ID? (Message 1918831)
Posted 14 Feb 2018 by Profile [SETI.Germany] Sutaru Tsureku (aka Dirk :-)
Post:
Hello

I detached, attached a PC here at SETI.
Normally he would get the old host ID.
Today it didn't worked like this.
The PC got a new host ID.

For some time I read a trick that the PC can use again the old host ID.
I searched the web but didn't found it.

Someone could show me the way to the trick?

Thanks
15) Message boards : News : Projects are (no longer) down (Message 1911393)
Posted 7 Jan 2018 by Profile [SETI.Germany] Sutaru Tsureku (aka Dirk :-)
Post:
Eric Korpela wrote:
(...)
And you've probably noticed that we are out of Arecibo data. We don't have a good idea of when we'll get more.

Why is that - what's the problem?
16) Message boards : News : We're generating work again. (Message 1904378)
Posted 2 Dec 2017 by Profile [SETI.Germany] Sutaru Tsureku (aka Dirk :-)
Post:
Eric Korpela wrote:
It took a bit longer than I thought it would, but we're back online. It'll probably be a few days before we have a full ready-to-send queue.

Now we can get back to finding ET.


Thanks.

I'm happy that my PCs can crunch again SETI tasks.

Einstein and MilkyWay were happy during the SETI downtime.

A PC in the top 20 hosts at SETI (which I have) idle every week during tuesday's SETI server maintenance. :-(

[sarcasm and sadness]
17) Message boards : Number crunching : Windows Update - Microsoft .NET Framework Update KB3186539 and KB4041085, KB4043767 (Message 1899228)
Posted 5 Nov 2017 by Profile [SETI.Germany] Sutaru Tsureku (aka Dirk :-)
Post:
For some time Windows Update (Win8.1 x64, Core and Pro versions) offered me:

Microsoft .NET Framework 4.7 for Windows 8.1 and Windows Server 2012 R2 for x64 (KB3186539)

I made a web search and they said it shouldn't be installed, because something will be 'destroyed' - so I have hidden it (not installed).


Windows Update offered me now:

2017-09 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7 on Windows 8.1 and Server 2012 R2 for x64 (KB4041085)

2017-10 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7 on Windows 8.1 and Server 2012 R2 for x64 (KB4043767)


What should I do now with the old not installed KB3186539 update,
I should install it now, because the two newer updates will repair the destroyed part,
or I should install the two newest updates and let hidden the KB3186539 update?


Thanks
18) Message boards : Number crunching : BUG Report: 3rd result don't validate, because the 1st & 2nd result validated already (Message 1854043)
Posted 9 Mar 2017 by Profile [SETI.Germany] Sutaru Tsureku (aka Dirk :-)
Post:
Here are the results...

Because for better overview - uninteresting I have made very small (not readable).
If interested - copy it to e.g. Notepad and it's displayed in readable size.


1st result:
Task 5503955182
Name ap_19no09ab_B0_P0_00281_20170210_21323.wu_0
Workunit 2429434010
Created 11 Feb 2017, 5:00:43 UTC
Sent 11 Feb 2017, 5:00:46 UTC
Report deadline 8 Mar 2017, 5:00:46 UTC
Received 13 Feb 2017, 6:18:15 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x00000000)
Computer ID 7203873
Run time 9 hours 27 min 20 sec
CPU time 9 hours 9 min 29 sec
Validate state Valid
Credit 574.94
Device peak FLOPS 0.00 GFLOPS
Application version AstroPulse v7
Anonymous platform (CPU)
Peak working set size 21.98 MB
Peak swap size 18.02 MB
Peak disk usage 5.04 MB
Stderr output

<core_client_version>7.6.33</core_client_version>
<![CDATA[
<stderr_txt>

Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64
CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX
AstroPulse v7 Windows x64 rev 2692, V7 match, by Raistmer with support of Lunatics.kwsn.net team.
by Lunatics team. Built with uncommitted modifications
state.fold_buf_size_short=65536; state.fold_buf_size_long=262144

Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64
CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX
### Restart at 47.02 percent.
state.fold_buf_size_short=65536; state.fold_buf_size_long=262144

Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64
CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX
### Restart at 47.02 percent.
state.fold_buf_size_short=65536; state.fold_buf_size_long=262144

Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64
CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX
### Restart at 47.97 percent.
state.fold_buf_size_short=65536; state.fold_buf_size_long=262144

Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64
CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX
### Restart at 47.97 percent.
state.fold_buf_size_short=65536; state.fold_buf_size_long=262144

Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64
CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX
### Restart at 50.56 percent.
state.fold_buf_size_short=65536; state.fold_buf_size_long=262144

Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64
CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX
### Restart at 50.56 percent.
state.fold_buf_size_short=65536; state.fold_buf_size_long=262144

Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64
CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX
### Restart at 50.56 percent.
state.fold_buf_size_short=65536; state.fold_buf_size_long=262144

Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64
CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX
### Restart at 52.53 percent.
state.fold_buf_size_short=65536; state.fold_buf_size_long=262144

Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64
CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX
### Restart at 52.53 percent.
state.fold_buf_size_short=65536; state.fold_buf_size_long=262144

Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64
CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX
### Restart at 61.60 percent.
state.fold_buf_size_short=65536; state.fold_buf_size_long=262144

Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64
CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX
### Restart at 62.22 percent.
state.fold_buf_size_short=65536; state.fold_buf_size_long=262144

Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64
CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX
### Restart at 64.13 percent.
state.fold_buf_size_short=65536; state.fold_buf_size_long=262144

Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64
CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX
### Restart at 67.06 percent.
state.fold_buf_size_short=65536; state.fold_buf_size_long=262144

Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64
CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX
### Restart at 71.28 percent.
state.fold_buf_size_short=65536; state.fold_buf_size_long=262144

Build features: Non-graphics BLANKIT TWINDECHIRP USE_LRINT FFTW USE_INCREASED_PRECISION USE_AVX x64
CPUID: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX
### Restart at 82.26 percent.
state.fold_buf_size_short=65536; state.fold_buf_size_long=262144

single pulses: 0
repetitive pulses: 0
percent blanked: 8.16


class T_remove_radar: total=1.20e+009, N=1, <>=1.20e+009, min=1.20e+009, max=1.20e+009
class T_main_loop_L1: total=1.89e+013, N=20, <>=9.44e+011, min=5.41e+011, max=1.13e+012
class T_FFT_forward: total=3.13e+011, N=291345, <>=1.07e+006, min=4.91e+005, max=1.09e+008
class T_remove_radar_randomize: total=6.82e+008, N=291345, <>=2.34e+003, min=8.81e+002, max=1.96e+006
class T_build_chirp_table: total=1.72e+010, N=155, <>=1.11e+008, min=1.04e+008, max=1.60e+008
class T_dechirp: total=2.58e+012, N=9323027, <>=2.77e+005, min=1.80e+001, max=1.61e+008
class T_FFT_inverse: total=8.49e+012, N=9323027, <>=9.10e+005, min=4.07e+005, max=1.62e+008
class T_ffa: total=4.28e+012, N=350, <>=1.22e+010, min=4.09e+009, max=7.73e+010

FFA blocks counters:
class T_FFA_fetch: total=3.60e+012, N=21350570, <>=1.69e+005, min=3.93e+004, max=1.36e+008
class T_FFA_tt_build: total=0.00e+000, N=0, <>=0.00e+000, min=1.84e+019, max=0.00e+000
class T_FFA_compare: total=3.55e+011, N=905365320, <>=3.91e+002, min=1.80e+001, max=1.06e+008
class T_FFA_coadd: total=1.84e+011, N=905365320, <>=2.03e+002, min=1.80e+001, max=1.06e+008
class T_FFA_stride_add: total=1.87e+010, N=183248010, <>=1.01e+002, min=1.80e+001, max=5.32e+007
USE_INCREASED_PRECISION SMALL_CHIRP_TABLE BLANKIT TWINDECHIRP USE_LRINT
rev 2692
00:16:05 (1720): called boinc_finish(0)

</stderr_txt>
]]>




2nd result (stock CPU app, so no result shown):
Task 5503955183
Name ap_19no09ab_B0_P0_00281_20170210_21323.wu_1
Workunit 2429434010
Created 11 Feb 2017, 5:00:43 UTC
Sent 11 Feb 2017, 5:00:45 UTC
Report deadline 8 Mar 2017, 5:00:45 UTC
Received 8 Mar 2017, 8:23:04 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x00000000)
Computer ID 7468551
Run time 1 days 20 hours 30 min 43 sec
CPU time 22 hours 31 min 27 sec
Validate state Valid
Credit 574.94
Device peak FLOPS 3.54 GFLOPS
Application version AstroPulse v7 v7.00
x86_64-pc-linux-gnu
Stderr output

<core_client_version>7.2.42</core_client_version>
<![CDATA[
<stderr_txt>
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
Counts single:rep. 0:0 Starting large chunk at dm 896
Counts single:rep. 0:0 Starting large chunk at dm 1024
Counts single:rep. 0:0 Starting large chunk at dm 1152
Counts single:rep. 0:0 Starting large chunk at dm 1280
Counts single:rep. 0:0 Starting large chunk at dm 1408
Counts single:rep. 0:0 Starting large chunk at dm 1536
Counts single:rep. 0:0 Starting large chunk at dm 1664
Counts single:rep. 0:0 Starting large chunk at dm 1792
Counts single:rep. 0:0 Starting large chunk at dm 1920
Counts single:rep. 0:0 Starting large chunk at dm 2048
Counts single:rep. 0:0 Starting large chunk at dm 2176
Counts single:rep. 0:0 Starting large chunk at dm 2304
Counts single:rep. 0:0 Starting large chunk at dm 2432
Counts single:rep. 0:0 Starting large chunk at dm 2560
Counts single:rep. 0:0 Starting large chunk at dm 2688
Counts single:rep. 0:0 Starting large chunk at dm 2816
Counts single:rep. 0:0 Starting large chunk at dm 2944
Counts single:rep. 0:0 Starting large chunk at dm 3072
Counts single:rep. 0:0 Starting large chunk at dm 3200
Counts single:rep. 0:0 Starting large chunk at dm 3328
Counts single:rep. 0:0 Starting large chunk at dm 3456
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
Counts single:rep. 0:0 Starting large chunk at dm 3456
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
Counts single:rep. 0:0 Starting large chunk at dm 3456
Counts single:rep. 0:0 Starting large chunk at dm 3584
Counts single:rep. 0:0 Starting large chunk at dm 3712
Counts single:rep. 0:0 Starting large chunk at dm 3840
Counts single:rep. 0:0 Starting large chunk at dm 3968
Counts single:rep. 0:0 Starting large chunk at dm 4096
Counts single:rep. 0:0 Starting large chunk at dm 4224
Counts single:rep. 0:0 Starting large chunk at dm 4352
Counts single:rep. 0:0 Starting large chunk at dm 4480
Counts single:rep. 0:0 Starting large chunk at dm 4608
Counts single:rep. 0:0 Starting large chunk at dm 4736
Counts single:rep. 0:0 Starting large chunk at dm 4864
Counts single:rep. 0:0 Starting large chunk at dm 4992
Counts single:rep. 0:0 Starting large chunk at dm 5120
Counts single:rep. 0:0 Starting large chunk at dm 5248
Counts single:rep. 0:0 Starting large chunk at dm 5376
Counts single:rep. 0:0 Starting large chunk at dm 5504
Counts single:rep. 0:0 Starting large chunk at dm 5632
Counts single:rep. 0:0 Starting large chunk at dm 5760
Counts single:rep. 0:0 Starting large chunk at dm 5888
Counts single:rep. 0:0 Starting large chunk at dm 6016
Counts single:rep. 0:0 Starting large chunk at dm 6144
Counts single:rep. 0:0 Starting large chunk at dm 6272
Counts single:rep. 0:0 Starting large chunk at dm 6400
Counts single:rep. 0:0 Starting large chunk at dm 6528
Counts single:rep. 0:0 Starting large chunk at dm 6656
Counts single:rep. 0:0 Starting large chunk at dm 6784
Counts single:rep. 0:0 Starting large chunk at dm 6912
Counts single:rep. 0:0 Starting large chunk at dm 7040
Counts single:rep. 0:0 Starting large chunk at dm 7168
Counts single:rep. 0:0 Starting large chunk at dm 7296
Counts single:rep. 0:0 Starting large chunk at dm 7424
Counts single:rep. 0:0 Starting large chunk at dm 7552
Counts single:rep. 0:0 Starting large chunk at dm 7680
Counts single:rep. 0:0 Starting large chunk at dm 7808
Counts single:rep. 0:0 Starting large chunk at dm 7936
Counts single:rep. 0:0 Starting large chunk at dm 8064
Counts single:rep. 0:0 Starting large chunk at dm 8192
Counts single:rep. 0:0 Starting large chunk at dm 8320
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
Counts single:rep. 0:0 Starting large chunk at dm 8320
Counts single:rep. 0:0 Starting large chunk at dm 8448
Counts single:rep. 0:0 Starting large chunk at dm 8576
Counts single:rep. 0:0 Starting large chunk at dm 8704
Counts single:rep. 0:0 Starting large chunk at dm 8832
Counts single:rep. 0:0 Starting large chunk at dm 8960
Counts single:rep. 0:0 Starting large chunk at dm 9088
Counts single:rep. 0:0 Starting large chunk at dm 9216
Counts single:rep. 0:0 Starting large chunk at dm 9344
Counts single:rep. 0:0 Starting large chunk at dm 9472
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
Counts single:rep. 0:0 Starting large chunk at dm 9472
Counts single:rep. 0:0 Starting large chunk at dm 9600
Counts single:rep. 0:0 Starting large chunk at dm 9728
Counts single:rep. 0:0 Starting large chunk at dm 9856
Counts single:rep. 0:0 Starting large chunk at dm 9984
Counts single:rep. 0:0 Starting large chunk at dm 10112
Counts single:rep. 0:0 Starting large chunk at dm 10240
Counts single:rep. 0:0 Starting large chunk at dm 10368
Counts single:rep. 0:0 Starting large chunk at dm 10496
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
Counts single:rep. 0:0 Starting large chunk at dm 10496
Counts single:rep. 0:0 Starting large chunk at dm 10624
Counts single:rep. 0:0 Starting large chunk at dm 10752
Counts single:rep. 0:0 Starting large chunk at dm 10880
Counts single:rep. 0:0 Starting large chunk at dm 11008
Counts single:rep. 0:0 Starting large chunk at dm 11136
Counts single:rep. 0:0 Starting large chunk at dm 11264
Counts single:rep. 0:0 Starting large chunk at dm 11392
Counts single:rep. 0:0 Starting large chunk at dm 11520
Counts single:rep. 0:0 Starting large chunk at dm 11648
Counts single:rep. 0:0 Starting large chunk at dm 11776
Counts single:rep. 0:0 Starting large chunk at dm 11904
Counts single:rep. 0:0 Starting large chunk at dm 12032
Counts single:rep. 0:0 Starting large chunk at dm 12160
Counts single:rep. 0:0 Starting large chunk at dm 12288
Counts single:rep. 0:0 Starting large chunk at dm 12416
Counts single:rep. 0:0 Starting large chunk at dm 12544
Counts single:rep. 0:0 Starting large chunk at dm 12672
Counts single:rep. 0:0 Starting large chunk at dm 12800
Counts single:rep. 0:0 Starting large chunk at dm 12928
Counts single:rep. 0:0 Starting large chunk at dm 13056
Counts single:rep. 0:0 Starting large chunk at dm 13184
Counts single:rep. 0:0 Starting large chunk at dm 13312
Counts single:rep. 0:0 Starting large chunk at dm 13440
Counts single:rep. 0:0 Starting large chunk at dm 13568
Counts single:rep. 0:0 Starting large chunk at dm 13696
Counts single:rep. 0:0 Starting large chunk at dm 13824
Counts single:rep. 0:0 Starting large chunk at dm 13952
Counts single:rep. 0:0 Starting large chunk at dm 14080
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
Counts single:rep. 0:0 Starting large chunk at dm 14080
Counts single:rep. 0:0 Starting large chunk at dm 14208
Counts single:rep. 0:0 Starting large chunk at dm 14336
Counts single:rep. 0:0 Starting large chunk at dm 14464
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
Counts single:rep. 0:0 Starting large chunk at dm 14464
Counts single:rep. 0:0 Starting large chunk at dm 14592
Counts single:rep. 0:0 Starting large chunk at dm 14720
Counts single:rep. 0:0 Starting large chunk at dm 14848
Counts single:rep. 0:0 Starting large chunk at dm 14976

11:22:46 (2085): called boinc_finish(0)

</stderr_txt>
]]>




3rd result (my):
Task 5567860620
Name ap_19no09ab_B0_P0_00281_20170210_21323.wu_2
Workunit 2429434010
Created 8 Mar 2017, 5:00:46 UTC
Sent 8 Mar 2017, 5:00:48 UTC
Report deadline 2 Apr 2017, 5:00:48 UTC
Received 8 Mar 2017, 11:03:29 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x00000000)
Computer ID 8221594
Run time 9 min 24 sec
CPU time 2 min 48 sec
Validate state Invalid
Credit 0.00
Device peak FLOPS 8,601.60 GFLOPS
Application version AstroPulse v7
Anonymous platform (ATI GPU)
Peak working set size 102.40 MB
Peak swap size 98.18 MB
Peak disk usage 0.04 MB
Stderr output

<core_client_version>7.6.33</core_client_version>
<![CDATA[
<stderr_txt>
Running on device number: 3
Verbose level set to:0
DATA_CHUNK_UNROLL set to:18
FFA thread block override value:2830
FFA thread fetchblock override value:2830
TUNE: kernel 1 now has workgroup size of (64,4,1)
TUNE: kernel 2 now has workgroup size of (64,4,1)
oclFFT plan class overrides requested: global radix 256; local radix 16; max workgroup size 256
Priority of worker thread raised successfully
Priority of process adjusted successfully, high priority class used
OpenCL platform detected: Advanced Micro Devices, Inc.
BOINC assigns device 3
Info: BOINC provided OpenCL device ID used
Used GPU device parameters are:
Number of compute units: 64
Single buffer allocation size: 256MB
Total device global memory: 3072MB
max WG size: 256
local mem type: Real

Build features: Non-graphics BLANKIT OpenCL TWIN_FFA OCL_ZERO_COPY COMBINED_DECHIRP_KERNEL FFTW USE_INCREASED_PRECISION USE_SSE2 x86
CPUID: Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX
AstroPulse v7 Windows x86 rev 2742, V7 match, by Raistmer with support of Lunatics.kwsn.net team. SSE2

OpenCL version by Raistmer

oclFFT fix for ATI GPUs by Urs Echternacht
ffa threshold mods by Joe Segur
SSE3 dechirping by JDWhale
Combined dechirp kernel by Frizz
Number of OpenCL platforms: 1


OpenCL Platform Name: AMD Accelerated Parallel Processing
Number of devices: 4
Max compute units: 64
Max work group size: 256
Max clock frequency: 1050Mhz
Max memory allocation: 3018693957
Name: Fiji
Vendor: Advanced Micro Devices, Inc.
Driver version: 1912.5 (VM)
Version: OpenCL 2.0 AMD-APP (1912.5)
Max compute units: 64
Max work group size: 256
Max clock frequency: 1050Mhz
Max memory allocation: 3018693957
Name: Fiji
Vendor: Advanced Micro Devices, Inc.
Driver version: 1912.5 (VM)
Version: OpenCL 2.0 AMD-APP (1912.5)
Max compute units: 64
Max work group size: 256
Max clock frequency: 1050Mhz
Max memory allocation: 3018693957
Name: Fiji
Vendor: Advanced Micro Devices, Inc.
Driver version: 1912.5 (VM)
Version: OpenCL 2.0 AMD-APP (1912.5)
Max compute units: 64
Max work group size: 256
Max clock frequency: 1050Mhz
Max memory allocation: 3018693957
Name: Fiji
Vendor: Advanced Micro Devices, Inc.
Driver version: 1912.5 (VM)
Version: OpenCL 2.0 AMD-APP (1912.5)


state.fold_buf_size_short=65536; state.fold_buf_size_long=262144

single pulses: 0
repetitive pulses: 0
percent blanked: 8.30

TWIN_FFA OCL_ZERO_COPY USE_OPENCL OPENCL_WRITE USE_INCREASED_PRECISION SMALL_CHIRP_TABLE COMBINED_DECHIRP_KERNEL BLANKIT
rev 2742
GPU device sync requested... ...GPU device synched
12:00:25 (2304): called boinc_finish(0)

</stderr_txt>
]]>




1st result:
single pulses: 0
repetitive pulses: 0
percent blanked: 8.16

3rd result (my):
single pulses: 0
repetitive pulses: 0
percent blanked: 8.30


I don't think that the result is not the same. ;-)

The small difference because '% blanked' is 'normal'.

My/this PC is running with this setup since 1 1/2 years (October '15) and never got invalid AP results with (up to the latest 'stable' version) Crimson 15.12 (1912.5 driver in it).
19) Message boards : Number crunching : BUG Report: 3rd result don't validate, because the 1st & 2nd result validated already (Message 1854026)
Posted 9 Mar 2017 by Profile [SETI.Germany] Sutaru Tsureku (aka Dirk :-)
Post:
AFAIK, this happen since a few years...

No solution possible?

1st and 2nd WU send out.
1st result came.
2st result missed the deadline.
A 3rd WU send out.
Now the 2nd result come after deadline.
1st and 2nd result validate.
3rd result come and get an invalid.


Example:
http://setiathome.berkeley.edu/workunit.php?wuid=2429434010

Workunit 2429434010
name ap_19no09ab_B0_P0_00281_20170210_21323.wu
application AstroPulse v7
created 11 Feb 2017, 5:00:39 UTC
canonical result 5503955182
granted credit 574.94
minimum quorum 2
initial replication 2
max # of error/total/success tasks 5, 10, 10
Task click for details - Computer - Sent - Time reported or deadline explain - Status - Run time (sec) - CPU time (sec) - Credit - Application
5503955182 - 7203873 - 11 Feb 2017, 5:00:46 UTC - 13 Feb 2017, 6:18:15 UTC - Completed and validated - 34,040.02 - 32,969.24 - 574.94 - AstroPulse v7 Anonymous platform (CPU)
5503955183 - 7468551 - 11 Feb 2017, 5:00:45 UTC - 8 Mar 2017, 8:23:04 UTC - Completed and validated - 160,243.22 - 81,087.37 - 574.94 - AstroPulse v7 v7.00 x86_64-pc-linux-gnu
5567860620 - 8021868 - 8 Mar 2017, 5:00:48 UTC - 8 Mar 2017, 11:03:29 UTC - Completed, marked as invalid - 564.59 - 168.47 - 0.00 - AstroPulse v7 Anonymous platform (ATI GPU)


Is this 'just' an AP thing, or this happens also with MB (SETI) results?


Thanks.


BTW.
No, no... ;-) My AMD Radeon R9 Fury X VGA cards use still Crimson 15.12 with 1912.5 driver in it - software/drivers after make invalid AP results... - because of my experiences with tests of all (7) software/drivers after up to Crimson 16.3.2.
20) Message boards : Number crunching : PCIe x1 GPU cards? (Message 1853473)
Posted 6 Mar 2017 by Profile [SETI.Germany] Sutaru Tsureku (aka Dirk :-)
Post:
After some time (1 3/4 years), which VGA cards with x1 plug are available now?


If I looked correct, this is the card which is available now:

ZOTAC GeForce GT 710, 1024MB DDR3, PCIe 2.0 x1, VGA, DVI, HDMI (ZT-71304-20L)


I have the:
ZOTAC GeForce GT 730, 1024MB, LP, Passiv, PCIe 2.0 x1 (ZT-71107-10L)
...installed. The above GT 710 would be a step back. ;-)


AMD's FirePro and NVIDIA's NVS could calculate also SETI's AP & MB WUs?


You know maybe other VGA cards with x1 plug which are available now?


Thanks.


Next 20


 
©2018 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.