Message boards :
AstroPulse :
app_config.xml syntax for command line passing
Message board moderation
Author | Message |
---|---|
![]() ![]() Send message Joined: 18 Aug 05 Posts: 2423 Credit: 15,878,738 RAC: 0 ![]() |
I'm trying one more time to pass command line params to stock app purely via BOINC own engine, w/o using app-specific config files. So I created such app_config.xml: <app_config> <app> <name>astropulse_v7</name> <gpu_versions> <gpu_usage>.5</gpu_usage> <cpu_usage>.01</cpu_usage> </gpu_versions> </app> <app_version> <app_name>astropulse_v7</app_name> <plan_class>opencl_ati_100</plan_class> <cmdline>-cpu_lock -instances_per_device 2</cmdline> </app_version> </app_config> Unfortunately, there are no any signs that application received provided command line options. Should it? Or I doing something wrong ? News about SETI opt app releases: https://twitter.com/Raistmer |
Send message Joined: 3 Jan 07 Posts: 1451 Credit: 3,272,268 RAC: 0 ![]() |
None of your computers at Beta are yet showing the BOINC v7.2.39 or higher required for the <app_version> construct to be recognised in app_config. |
![]() ![]() Send message Joined: 18 Aug 05 Posts: 2423 Credit: 15,878,738 RAC: 0 ![]() |
None of your computers at Beta are yet showing the BOINC v7.2.39 or higher required for the <app_version> construct to be recognised in app_config. I see, thanks. News about SETI opt app releases: https://twitter.com/Raistmer |
![]() ![]() Send message Joined: 18 Aug 05 Posts: 2423 Credit: 15,878,738 RAC: 0 ![]() |
Now I'm trying it on BOINc 7.4.x client. Got next notice: SETI@home Beta Test: Notice from BOINC Hope it just goes away when some AP tasks will be actually downloaded (after DB repair)... News about SETI opt app releases: https://twitter.com/Raistmer |
Send message Joined: 30 Dec 13 Posts: 258 Credit: 12,340,341 RAC: 0 ![]() |
It always does that the first time you launch Boinc. Once the server downloads all the files for AP v7 to run, it will go away. |
![]() ![]() Send message Joined: 18 Aug 05 Posts: 2423 Credit: 15,878,738 RAC: 0 ![]() |
I can confirm that updating to current recommended BOINC version allowed to use command line options via app_config.xml file. This make separate config text file unneeded for new BOINC clients. News about SETI opt app releases: https://twitter.com/Raistmer |
![]() Send message Joined: 11 Dec 14 Posts: 96 Credit: 1,240,941 RAC: 0 ![]() |
I can confirm that updating to current recommended BOINC version allowed to use command line options via app_config.xml file. This make separate config text file unneeded for new BOINC clients. So, how would I specify device0, device1, device2, etc. (where each is a different NVIDIA GPU), with this method? Or have I misunderstood what's changing here? |
Send message Joined: 30 Dec 13 Posts: 258 Credit: 12,340,341 RAC: 0 ![]() |
i don't like BOINC 7.4.x Had problems with it on other projects that resolved when I moved back to 7.2.42 Probably ok if I only stuck with Seti or beta but otherwise... my 2 cents Zalster |
![]() ![]() Send message Joined: 18 Aug 05 Posts: 2423 Credit: 15,878,738 RAC: 0 ![]() |
I can confirm that updating to current recommended BOINC version allowed to use command line options via app_config.xml file. This make separate config text file unneeded for new BOINC clients. It's about command line options only. News about SETI opt app releases: https://twitter.com/Raistmer |
©2021 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.