NEW BOINC add-on 'SETIspirit' for SETI@home users

Message boards : Number crunching : NEW BOINC add-on 'SETIspirit' for SETI@home users
Message board moderation

To post messages, you must log in.

Previous · 1 · 2 · 3 · Next

AuthorMessage
Profile BilBg
Volunteer tester
Avatar

Send message
Joined: 27 May 07
Posts: 3720
Credit: 9,385,827
RAC: 0
Bulgaria
Message 1385173 - Posted: 27 Jun 2013, 18:15:38 UTC - in response to Message 1384901.  

1) Where is the file stdoutdae.archiv created?
C:\Users\<Your Username>\AppData\Roaming\SETIspirit\stdoutdae.archiv

On Windows XP this will be probably:
C:\Documents and Settings\<Your Username>\Application Data\SETIspirit\stdoutdae.archiv

Or in generic form (will this work on any Windows?):
%APPDATA%\SETIspirit\stdoutdae.archiv

Or will it be here?:
C:\Documents and Settings\<Your Username>\Local Settings\Application Data\SETIspirit\stdoutdae.archiv

Do you show this directory (%APPDATA%\SETIspirit\) somewhere in Settings?
(With option to change it? With button to easy open it?)


SETIspirit is automatically archiving the stdoutdae.old file by appending it to stdoutdae.archiv and deleting the stdoutdae.old file

a) SETIspirit is opening any files read-only and is doing this ALWAYS without locking (non exclusive access only)

Don't you think the above two slightly contradict?
You are careful to not affect BOINC operations and files but you delete the stdoutdae.old (probably you do this to avoid adding it again and again to stdoutdae.archiv)
(Yes, BOINC replaces stdoutdae.old but only after stdoutdae.txt grows to the <max_stdout_file_size>)

We often tell users: "If you restarted BOINC the previous messages can be found in stdoutdae.txt and stdoutdae.old"
If BOINC just replaced stdoutdae.old and SETIspirit just deleted it the user is left with only a very small stdoutdae.txt to look in.

Suggestions how to avoid this:

A) Give SETIspirit user a choice in Settings:
What do you want SETIspirit to do with stdoutdae.old (BOINC file) after appending it to stdoutdae.archiv (SETIspirit file)?
( ) Delete stdoutdae.old
(*) Rename stdoutdae.old to stdoutdae_{date}_{time}.old

(for {date}_{time} the user format can't be used as delimiters like "/" ":" make the filename invalid.
Good format may be like: 2013-06-27_13-52-13
The {date}_{time} have to be the stdoutdae.old file modification date/time and not the current date/time
)

I think the default have to be 'Rename' but you may ask user (at installation/first start/first usage of stdoutdae.old)


or B) After appending it to stdoutdae.archiv add a 'signature' line at the end of stdoutdae.old to mark it 'already used' (the bad thing is this changes both the file and its modification date/time), e.g.:
SETIspirit appended this file to stdoutdae.archiv on 2013-06-27 13-52-13 {{SETIspirit}}


or C) Remember some properties of the last appended stdoutdae.old like:
Exact size (bytes) of stdoutdae.old (it is slightly different every time)
Modification date/time
Calculate some kind of checksum of stdoutdae.old (e.g. MD5 or just CRC32)
Remember the first line (or first 10-100 lines) of stdoutdae.old (it is different every time as it have date/time):
28-Apr-2013 01:50:02 [SETI@home] Scheduler request completed: got 0 new tasks


 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 
ID: 1385173 · Report as offensive
Profile BilBg
Volunteer tester
Avatar

Send message
Joined: 27 May 07
Posts: 3720
Credit: 9,385,827
RAC: 0
Bulgaria
Message 1385177 - Posted: 27 Jun 2013, 18:45:26 UTC - in response to Message 1384919.  

As a result of this bugs the SETIspirit debug logfile...

C:\Users\<Your Username>\AppData\Roaming\SETIspirit\debug.log

is may be grown into a large file. You can safely delete the debug file from your harddisk (please quit SETIspirit first), it will be automatically re-created the next time SETIspirit starts.

Better if SETIspirit (in next version) will take care of this by itself:
On every start of SETIspirit (and/or in regular intervals 1-24 h) check the 'age' of debug.log
If it's older (creation time) than 1 day - rename it (e.g. to debug_{date}_{time}.log)

Delete the 'very old' debug_{date}_{time}.log files after a period (user settable?) of 7-30 days
(i.e. if any debug*.log file is older than 7-30 days - delete it)


 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 
ID: 1385177 · Report as offensive
Profile dschwarting
Avatar

Send message
Joined: 7 Sep 99
Posts: 105
Credit: 56,980,300
RAC: 16,609
Germany
Message 1385179 - Posted: 27 Jun 2013, 19:04:57 UTC - in response to Message 1385173.  

1) Where is the file stdoutdae.archiv created?
C:\Users\<Your Username>\AppData\Roaming\SETIspirit\stdoutdae.archiv

On Windows XP this will be probably:
C:\Documents and Settings\<Your Username>\Application Data\SETIspirit\stdoutdae.archiv

Or in generic form (will this work on any Windows?):
%APPDATA%\SETIspirit\stdoutdae.archiv

Or will it be here?:
C:\Documents and Settings\<Your Username>\Local Settings\Application Data\SETIspirit\stdoutdae.archiv

Do you show this directory (%APPDATA%\SETIspirit\) somewhere in Settings?
(With option to change it? With button to easy open it?)


SETIspirit is automatically archiving the stdoutdae.old file by appending it to stdoutdae.archiv and deleting the stdoutdae.old file

a) SETIspirit is opening any files read-only and is doing this ALWAYS without locking (non exclusive access only)

Don't you think the above two slightly contradict?
You are careful to not affect BOINC operations and files but you delete the stdoutdae.old (probably you do this to avoid adding it again and again to stdoutdae.archiv)
(Yes, BOINC replaces stdoutdae.old but only after stdoutdae.txt grows to the <max_stdout_file_size>)

We often tell users: "If you restarted BOINC the previous messages can be found in stdoutdae.txt and stdoutdae.old"
If BOINC just replaced stdoutdae.old and SETIspirit just deleted it the user is left with only a very small stdoutdae.txt to look in.

Suggestions how to avoid this:

A) Give SETIspirit user a choice in Settings:
What do you want SETIspirit to do with stdoutdae.old (BOINC file) after appending it to stdoutdae.archiv (SETIspirit file)?
( ) Delete stdoutdae.old
(*) Rename stdoutdae.old to stdoutdae_{date}_{time}.old

(for {date}_{time} the user format can't be used as delimiters like "/" ":" make the filename invalid.
Good format may be like: 2013-06-27_13-52-13
The {date}_{time} have to be the stdoutdae.old file modification date/time and not the current date/time
)

I think the default have to be 'Rename' but you may ask user (at installation/first start/first usage of stdoutdae.old)


or B) After appending it to stdoutdae.archiv add a 'signature' line at the end of stdoutdae.old to mark it 'already used' (the bad thing is this changes both the file and its modification date/time), e.g.:
SETIspirit appended this file to stdoutdae.archiv on 2013-06-27 13-52-13 {{SETIspirit}}


or C) Remember some properties of the last appended stdoutdae.old like:
Exact size (bytes) of stdoutdae.old (it is slightly different every time)
Modification date/time
Calculate some kind of checksum of stdoutdae.old (e.g. MD5 or just CRC32)
Remember the first line (or first 10-100 lines) of stdoutdae.old (it is different every time as it have date/time):
28-Apr-2013 01:50:02 [SETI@home] Scheduler request completed: got 0 new tasks



Thanks for your thoughts and suggestions. I'll change the stdoutdae.old issue that SETIspirit will handle this in the manner the user wants.

Regards,
Dirk
SETIspirit Homepage
ID: 1385179 · Report as offensive
Profile Mike Bader Project Donor
Volunteer tester
Avatar

Send message
Joined: 18 May 99
Posts: 213
Credit: 17,935,451
RAC: 10,445
Message 1385183 - Posted: 27 Jun 2013, 19:20:11 UTC - in response to Message 1385118.  

I cycled through my work units ok.
slot 0 and slot 1


Mike Bader
BOINC V7.16.3
http://setiathome.berkeley.edu/team_join_form.php?id=5 - Join Our International Team
[img]http://boinc.mundayweb.com/one/stats.php?
ID: 1385183 · Report as offensive
Profile Mike Bader Project Donor
Volunteer tester
Avatar

Send message
Joined: 18 May 99
Posts: 213
Credit: 17,935,451
RAC: 10,445
Message 1385186 - Posted: 27 Jun 2013, 19:25:15 UTC - in response to Message 1385118.  

I tried all options for work unit, no issues here.
Mike Bader
BOINC V7.16.3
http://setiathome.berkeley.edu/team_join_form.php?id=5 - Join Our International Team
[img]http://boinc.mundayweb.com/one/stats.php?
ID: 1385186 · Report as offensive
Profile BilBg
Volunteer tester
Avatar

Send message
Joined: 27 May 07
Posts: 3720
Credit: 9,385,827
RAC: 0
Bulgaria
Message 1385194 - Posted: 27 Jun 2013, 19:37:05 UTC - in response to Message 1385179.  

Thanks for your thoughts and suggestions. I'll change the stdoutdae.old issue that SETIspirit will handle this in the manner the user wants.

You may combine A) and C) :

Give SETIspirit user a choice in Settings:

What do you want SETIspirit to do with stdoutdae.old (BOINC file) after appending it to stdoutdae.archiv (SETIspirit file)?
( ) Delete stdoutdae.old
( ) Rename stdoutdae.old to stdoutdae_{date}_{time}.old
(*) Don't touch stdoutdae.old (SETIspirit will remember that the file was already appended/used by its first line)


 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 
ID: 1385194 · Report as offensive
Profile dschwarting
Avatar

Send message
Joined: 7 Sep 99
Posts: 105
Credit: 56,980,300
RAC: 16,609
Germany
Message 1387299 - Posted: 3 Jul 2013, 18:04:32 UTC

Dear SETI@home number crunchers,

I'm very happy to release SETIspirit 1.0.9 today, it has new features, bug fixes and user requested enhancements. Thanks again for all your valueable feedbacks!

Here are some changes...

· new built-in update checks
· new settings form for directory-, log archiver- and update check options
· the <debug.log> file size is now monitored and limited to 10 MB
· improved processor detection (BOINC Environment)
· immediately SETIspirit termination if the operating system is shuting down
· RAC issue fixed

I would be happy to hear your feedback again.

Best regards,
Dirk


SETIspirit Homepage
ID: 1387299 · Report as offensive
Thomas
Volunteer tester

Send message
Joined: 9 Dec 11
Posts: 1499
Credit: 1,345,576
RAC: 0
France
Message 1387541 - Posted: 4 Jul 2013, 7:34:01 UTC - in response to Message 1387299.  

Thanks for this heads-up Dirk ! :)
ID: 1387541 · Report as offensive
Profile dschwarting
Avatar

Send message
Joined: 7 Sep 99
Posts: 105
Credit: 56,980,300
RAC: 16,609
Germany
Message 1389585 - Posted: 10 Jul 2013, 19:34:34 UTC

SETIspirit v1.1.0 is released now

with new features...

· the autocorrelation analysis results will now be shown in the wu monitor
· SETIspirit Skin for the BOINC Manager application added
· new BOINC Manager menu entry in the SETIspirit project button
· SETIspirit autostart options added
· improved SETIspirit gui (graphical user interface)
· when opening the sky map the wu monitor now shows the selected slot

and a small bugfix...

· recorded on: tags and analysis results of astropulse wu's will now be skipped,
· as SETIspirit currently could not determine it

Comments and feature requests are welcome!

Best regards,
Dirk

SETIspirit Homepage
ID: 1389585 · Report as offensive
Thomas
Volunteer tester

Send message
Joined: 9 Dec 11
Posts: 1499
Credit: 1,345,576
RAC: 0
France
Message 1389680 - Posted: 11 Jul 2013, 6:36:19 UTC - in response to Message 1389585.  

Thanks for the heads-up, Dirk.
It works !
The pop-up alert for the new update is great ! :)
ID: 1389680 · Report as offensive
Profile dschwarting
Avatar

Send message
Joined: 7 Sep 99
Posts: 105
Credit: 56,980,300
RAC: 16,609
Germany
Message 1390123 - Posted: 12 Jul 2013, 14:54:01 UTC

SETIspirit v1.1.2 is released now

with two bugfixes...

· zero month statistics issue fixed
· calculation of the wu position fixed (zero min sec ' '')

These bugs depends on the country settings of the operating system again. It isn't easy to develop error free applications for international use, as I don't have windows os with different languages at home.

But with user feedbacks and a little teamwork this bugs can be fixed easy.
Thx.

Best regards,
Dirk



SETIspirit Homepage
ID: 1390123 · Report as offensive
Profile Mark Wyzenbeek
Avatar

Send message
Joined: 28 Jun 99
Posts: 134
Credit: 6,203,079
RAC: 0
United States
Message 1390315 - Posted: 13 Jul 2013, 1:30:23 UTC - in response to Message 1390123.  

Thanks Dirk. Writing international code must be challenging.

I installed 1.1.2 and I still have nothing in my month statistics page. Should old work show up or do I have to wait til I finish a workunit for something to start showing up? Week and year pages look fine.
The Universe is not only stranger than you imagine, it's stranger than you can imagine.

SETI@home classic workunits 1,405 CPU time 57,318 hours
ID: 1390315 · Report as offensive
Thomas
Volunteer tester

Send message
Joined: 9 Dec 11
Posts: 1499
Credit: 1,345,576
RAC: 0
France
Message 1390335 - Posted: 13 Jul 2013, 4:03:21 UTC
Last modified: 13 Jul 2013, 4:03:30 UTC

Thanks for the heads-up, Dirk.
Month statistics page is OK for me for june & july (since I reinstalled BOINC Manager).
ID: 1390335 · Report as offensive
Profile dschwarting
Avatar

Send message
Joined: 7 Sep 99
Posts: 105
Credit: 56,980,300
RAC: 16,609
Germany
Message 1390374 - Posted: 13 Jul 2013, 8:26:26 UTC - in response to Message 1390315.  

Thanks Dirk. Writing international code must be challenging.

I installed 1.1.2 and I still have nothing in my month statistics page. Should old work show up or do I have to wait til I finish a workunit for something to start showing up? Week and year pages look fine.


Thanks for your feedback Mark,

the statistics will be immediately created if you are opening the statistics form, so you do not have to wait for a new finished workunit. Did you never have seen month statistics? Crazy! (but important to know for me)

With your help I would like to fix this.

Could you please send me a copy of the following files to info@setispirit.de (please zip the files)...

stdoutdae.txt (can be found in the boinc data directory)
stdoutdae.old (if existing, can be found in the boinc data directory)
stdoutdae.archiv (if existing, can be found in the SETIspirit data directory)
debug.log (can be found in the SETIspirit data directory)
debug.log.zip (if existing, can be found in the SETIspirit data directory)
screenshots of the SETIspirit main form, the week-, month- and year statistics
details to your os: windows version, 32bit/64bit, language

Please close the BOINC Manager and SETIspirit application before copying the files. This will allow me to track down the bug.

Thanks in advance.

Best regards,
Dirk


SETIspirit Homepage
ID: 1390374 · Report as offensive
Profile dschwarting
Avatar

Send message
Joined: 7 Sep 99
Posts: 105
Credit: 56,980,300
RAC: 16,609
Germany
Message 1390375 - Posted: 13 Jul 2013, 8:38:53 UTC - in response to Message 1390335.  

Thanks for the heads-up, Dirk.
Month statistics page is OK for me for june & july (since I reinstalled BOINC Manager).



Hi Thomas,

this is okay if you have first done a de-installation of the BOINC Manager (which will may be delete the log files in the boinc data directory) before you have installed a new BOINC Manager. Please look for the oldest entry shown in the stdoutdae.txt, stdoutdae.old or stdoutdae.archiv file. If this entry is from june SETIspirit works well. Thx.

Best regards,
Dirk


SETIspirit Homepage
ID: 1390375 · Report as offensive
Profile BilBg
Volunteer tester
Avatar

Send message
Joined: 27 May 07
Posts: 3720
Credit: 9,385,827
RAC: 0
Bulgaria
Message 1390381 - Posted: 13 Jul 2013, 10:00:16 UTC - in response to Message 1390375.  

this is okay if you have first done a de-installation of the BOINC Manager (which will may be delete the log files in the boinc data directory) before you have installed a new BOINC Manager.

De-installation of BOINC do not touch the BOINC Data directory - all files there remain intact.
Re-installation also do not start from scratch - continues to use the existing files in BOINC Data directory.


 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 
ID: 1390381 · Report as offensive
Thomas
Volunteer tester

Send message
Joined: 9 Dec 11
Posts: 1499
Credit: 1,345,576
RAC: 0
France
Message 1390399 - Posted: 13 Jul 2013, 13:03:07 UTC - in response to Message 1390375.  

Hi Thomas,

this is okay if you have first done a de-installation of the BOINC Manager (which will may be delete the log files in the boinc data directory) before you have installed a new BOINC Manager. Please look for the oldest entry shown in the stdoutdae.txt, stdoutdae.old or stdoutdae.archiv file. If this entry is from june SETIspirit works well. Thx.

Best regards,
Dirk

Dirk, I deleted all the files including the BOINC Data Directory because I had a big problem on my computer with BOINC Manager on may.
So I did spring cleaning.
That is certainly why it works...
And it's for this reason that I don't have much historical analysis in SETIspirit.
ID: 1390399 · Report as offensive
Profile John

Send message
Joined: 5 Jun 99
Posts: 30
Credit: 71,901,772
RAC: 20,991
United States
Message 1390453 - Posted: 13 Jul 2013, 19:46:10 UTC

I am finding SETIspirit very interesting with great promise. Just installed it yesterday. I look at the main screen and it says no GPU units completed. I have run non-gpu units when SETI runs out of AP's but generally AP's is all I run. I looked a couple places including SETIspirit.ini which says I have no useable GPU? I do run Lunatics optimized software and have a Nvidia GTX 470 as a GPU. The GPU runs 2 Seti units at a time (count=.5) and SETIspirit says I have completed 84 of them (probably since the install). So how do I get SETspirit to recognize my GPU? I run SETI on another computer and it appears to be OK as it recognizes the GPU (GTX 560). Also SETIspirit seems to be counting SIMAP WU's as SETI units on the computer with the GTX 470 as it says I have 300 SETI work units and that is the exact count of the SIMAP units(Not including the 10 AP units which it counted correctly. Thanks for a great program. Later. John
ID: 1390453 · Report as offensive
Profile dschwarting
Avatar

Send message
Joined: 7 Sep 99
Posts: 105
Credit: 56,980,300
RAC: 16,609
Germany
Message 1390701 - Posted: 14 Jul 2013, 18:30:42 UTC - in response to Message 1390453.  

I am finding SETIspirit very interesting with great promise. Just installed it yesterday. I look at the main screen and it says no GPU units completed. I have run non-gpu units when SETI runs out of AP's but generally AP's is all I run. I looked a couple places including SETIspirit.ini which says I have no useable GPU? I do run Lunatics optimized software and have a Nvidia GTX 470 as a GPU. The GPU runs 2 Seti units at a time (count=.5) and SETIspirit says I have completed 84 of them (probably since the install). So how do I get SETspirit to recognize my GPU? I run SETI on another computer and it appears to be OK as it recognizes the GPU (GTX 560). Also SETIspirit seems to be counting SIMAP WU's as SETI units on the computer with the GTX 470 as it says I have 300 SETI work units and that is the exact count of the SIMAP units(Not including the 10 AP units which it counted correctly. Thanks for a great program. Later. John


Hi John,

thanks for your feedback and interest to SETIspirit!

SETIspirit itself does not check the GPU hardware, instead of this it simply shows the gpu entries detected in the boinc manager logfile <stdoutdae.txt>. The "no useable gpu" message is caused by a SETIspirit bug, which is now fixed with the latest release v1.1.4. So whatever SETIspirit shows as gpu, it never effects the gpu number crunching (even with Lunatics).

So let's have a look how SETIspirit counts the completed (gpu) workunits...

In the SETI@home Project Status frame of the SETIspirit main form you can find the...

a) total AP WU's completed
b) total SETI@home WU's completed

counters. SETIspirit counts the number of <stdoutdae.txt> log entries with...

a) "[SETI@home] Finished upload of ap_" and
b) "[SETI@home] Finished upload of"

strings, where b = b - a.

For this cause, it's important to leave the file_xfer, task and sched_ops <log_flags> enabled (which is the boinc manager standard without cc_config.xml file). SETIspirit v1.1.4 now checks the required BOINC Manager log options and shows a warning if they are not met.

As the search strings includes a "[SETI@home]" tag, I don't think that SETIspirit is counting SIMAN wu's as SETI@home wu's.

Please try the latest SETIspirit release and report your experience.
Thx.

Best regards,
Dirk


SETIspirit Homepage
ID: 1390701 · Report as offensive
Profile dschwarting
Avatar

Send message
Joined: 7 Sep 99
Posts: 105
Credit: 56,980,300
RAC: 16,609
Germany
Message 1390703 - Posted: 14 Jul 2013, 18:37:56 UTC

SETIspirit v1.1.4 is released now

with new features...

· improved GPU detection
· long GPU descriptions will be shortened and shown as a tooltip
· the required BOINC Manager log options will be checked and named if not met

and a "second chance" bugfix...

· zero month statistics issue fixed (2nd try)

(nothing is as it seems ;-)

Best regards,
Dirk


SETIspirit Homepage
ID: 1390703 · Report as offensive
Previous · 1 · 2 · 3 · Next

Message boards : Number crunching : NEW BOINC add-on 'SETIspirit' for SETI@home users


 
©2019 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.