Re: [boinc_dev] Fwd: Project app selection reset

[David Anderson]

The project could use a larger value for :
https://boinc.berkeley.edu/trac/wiki/ProjectOptions#Appversionselection

If the project sets  they'll see info in
the scheduler log that will clarify what's happening.

-- David

On 11/11/2017 2:03 PM, TarotApprentice wrote:


Since the message below I have found the below config_aux entry. I have asked the 
project admin what values he has set. Other users have suggested its taking 1024 
tasks before trying a different app. Other than this is there anything else the 
project admin can do so it tries the various apps more quickly?


MarkJ

X
In predicting which app version will be faster for a given host, multiply 
the
projected FLOPS by a uniform random variable with mean 1 and this standard
deviation (default 0.1).


Begin forwarded message:

*From:* TarotApprentice >

*Date:* 5 November 2017 at 5:08:27 pm AEDT
*To:* BOINC Alpha >

*Subject:* *Project app selection reset*

I have an issue with Asteroids where the project app selection doesn’t work 
properly. They have 3 period search apps for the CPU, being sse2, sse3 and avx. 
All my x64 machines support avx as the highest instruction set available from the 
project. I have 4 identical Ryzen 7 Machine, two of which have received and are 
running the avx app. One got the sse2 and another got the sse3 app. None of them 
have tried the other apps according to the application details for each host.


Its not limited to AMD, I also have 8 i7’s-6700’s again identical builds and its 
a similar story. Six got the avx app, one the sse2 and the other one got the sse3 
app. Again no history of trying the other apps to determine the one with the 
highest APR. For these two “slow app” machines I have detached them from the 
project and am waiting on their 90 days of no contact before I can delete the 
host before reattaching it in the hope a new host record will start with the avx app.


Is there any way to get it to try the other apps like its supposed to, or at 
least to reset the host app details? I have contacted the admin, Kyong but he 
isn’t aware of anything he can do. I have also seen other people on their message 
boards complaining of the same problem.


MarkJ


___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] [boinc_alpha] Linux Releases on BOINC Download Page ??

[David Anderson]

On 11/13/2017 10:53 AM, Art Masson wrote:

The links and recommended versions on the BOINC download site for Linux are 
very old.

Can links to the latest Linux released versions be added to the BOINC Download 
site at

https://boinc.berkeley.edu/download_all.php  ??


Because of the differences between Linux distros,
the recommended way of installing BOINC is using a package manager.

However, we should offer our own installer, at least for testing purposes.
In the past our policy has been to offer a self-extracting archive installer
for the latest Ubuntu distribution.
Instructions for building this are here:
https://boinc.berkeley.edu/trac/wiki/CompileClient

This hasn't been done since 7.4.22 (Sept. 2014) because no one has
volunteered for the role of "linux builder" as described here:
https://boinc.berkeley.edu/trac/wiki/AdminRoles

If someone would like to volunteer, let me know.

-- David
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] [boinc_alpha] BOINC 7.8.4 for Mac

[Richard Haselgrove]

One report of 'cannot connect to client' with the new v7.8.4 on Mac OS X 
10.12.6 (Darwin 16.7.0)
Host has a HD 5750 which showed 1024MB under BOINC v7.8.3
Details at 
http://boinc.berkeley.edu/dev/forum_thread.php?id=11884=82924#82924 

On Friday, 10 November 2017, 22:27, Charlie Fenton 
 wrote:
 

 I have built BOINC 7.8.4 for the Mac and uploaded it to 
. This fixes the calculation of GPU memory when 
running under OS 10.13 High Sierra.

Cheers,
--Charlie

___
boinc_alpha mailing list
boinc_al...@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


   
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

[boinc_dev] Proposal for Use of GitHub Project Boards

[Kevin Reed]

Greetings,

I have seen previous discussions by at least Christian Beer and Vitalii
Koshura about using GitHub project boards.  I'd like to propose the
following guidelines for using them:
https://github.com/BOINC/boinc-policy/blob/project-boards/Issue_and_Pull_Request_Management.md

I've opened the following pull request to have this merged into the
BOINC/boinc-policy repository: https://github.com/BOINC/boinc-policy/pull/7
It would be great if we could have the discussion about the proposed
guidelines in the "conversation" section of the pull request.

The rationale for this change is that there are currently 339 issues that
can be seen here:  https://github.com/BOINC/boinc/issuesThis view of
issues makes it hard to see which ones belong to which component of BOINC,
which ones are higher priority than others and which ones have been
reviewed and are ready to implement vs ones that have been quickly opened
and don't have sufficient detail for a developer to implement.

If we use project boards, its makes it much easier for contributors to find
issues that pertain to a part of the system that they can contribute to and
that they know is important and ready to implement vs ones that are less
critical or are not ready to implement.

The goal for this proposal is for the guidelines to be simple and useful.
Please review and suggest ways to make the guidelines simpler and more
useful.

Since this is a development process document, it requires a consensus vote
of the committers as outlined in the governance document (
https://github.com/BOINC/boinc-policy/blob/project-boards/Governance.md#511-consensus-voting
).  What this means practically, is that we can discuss this for a week
updating the document based on comments and then if no-one objects, a
committer other than me can merge my pull request into the master branch of
boinc-policy.  In the future, if someone wants to change it, they simply
submit a pull request that changes the document which then starts another
discussion period.

Thanks,

Kevin

...

 knr...@us.ibm.com
 Donate your computer's unused power to humanitarian research:
www.worldcommunitygrid.org

WCG
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.