1) Message boards : Theory Application : Theory v.5.21 (Message 7032)
Posted 8 May 2020 by Profile Laurence
Post:
This new version updates the CVMFS configuration for the VM apps to improve the robustness with respect to temporary network issues. Some additional CVMFS information is shown in the output for debugging purposes.
2) Message boards : CMS Application : New Version 50.00 (Message 6998)
Posted 5 Mar 2020 by Profile Laurence
Post:
Cleaning up the CVMFS configuration so that it no long contacts the old proxy.
3) Message boards : Theory Application : New Version v5.19 (Message 6949)
Posted 16 Jan 2020 by Profile Laurence
Post:

I never tried before but now I am wondering if I can just copy this new version on a stick and put it on the other pc's so I only have to d/l this once.


The best thing to do would be to create a local caching proxy with squid. This will automatically do this without you having to intervene. It may take a bit of effort to setup but overall a lot less effort than doing it manually each time.
4) Message boards : Theory Application : New Version v5.19 (Message 6947)
Posted 16 Jan 2020 by Profile Laurence
Post:
I have updated all platforms. Please let me know if there are any issues.
5) Message boards : Theory Application : New Version v5.19 (Message 6945)
Posted 15 Jan 2020 by Profile Laurence
Post:
Version 5.20 should fix the issue.
6) Message boards : Theory Application : New Version v5.19 (Message 6944)
Posted 15 Jan 2020 by Profile Laurence
Post:
This only seems to be an issue with the Windows version.
7) Message boards : Theory Application : New Version v5.19 (Message 6940)
Posted 13 Jan 2020 by Profile Laurence
Post:
This seems to be working fine for me. I will put it in production tomorrow if there are no issues reported.
8) Message boards : Theory Application : New Version v5.19 (Message 6939)
Posted 13 Jan 2020 by Profile Laurence
Post:
This new version will consider failed jobs as successful from a BOINC perspective. This means that the error output will be returned to the MCPlots server for further analysis and they will not be re-run on other hosts.
9) Message boards : General Discussion : Simple Attach (Message 6891)
Posted 9 Dec 2019 by Profile Laurence
Post:
Thanks for trying! I think that if you click not installed it should download a BOINC client that is already attached to the project.
You could be right.

The 2 download links (BOINC and BOINC+VBox) are

boinc_7.14.2_windows_x86_64__18_10877416_1707115c.exe
and
boinc_7.14.2_windows_x86_64_vbox__18_10877416_1707115c.exe

where 10877416 is my new SETI-user-ID

Does it also work like this for you on LHC@home?
10) Message boards : General Discussion : Simple Attach (Message 6887)
Posted 6 Dec 2019 by Profile Laurence
Post:
Thanks for trying! I think that if you click not installed it should download a BOINC client that is already attached to the project.
11) Message boards : General Discussion : Simple Attach (Message 6885)
Posted 6 Dec 2019 by Profile Laurence
Post:
You may want to try on Seti@home first to see how it should work. I think it is join.php
12) Message boards : General Discussion : Simple Attach (Message 6883)
Posted 6 Dec 2019 by Profile Laurence
Post:
I suppose attaching with BOINC Simple View is meant.

No. This. It will only work on the production project.
13) Message boards : General Discussion : Simple Attach (Message 6879)
Posted 5 Dec 2019 by Profile Laurence
Post:
As far as I understand the Simple Attach mechanism is now available on LHC@home. Please could someone with a Windows machine give it try at let me know whether or not it works.
14) Message boards : General Discussion : Differences between apps (Message 6872)
Posted 3 Dec 2019 by Profile Laurence
Post:
There is no difference, just a different numbering scheme.
15) Message boards : General Discussion : Scheduler Change (Message 6860)
Posted 27 Nov 2019 by Profile Laurence
Post:
Thanks for testing. I am going to update the production sched as I think it is an improvement over what we have now.
16) Message boards : General Discussion : Scheduler Change (Message 6856)
Posted 27 Nov 2019 by Profile Laurence
Post:
There is still a small issue left to be solved. If I have 3 CPUs and have set Max 2 CPUs. The request will come back with 2 2 CPU jobs whereas I would like 1 2 CPU job and 1 1C PU job. If these are separate requests everything is fine. Anyway, I have opened an issue on the topic to hopefully get input from others.
17) Message boards : General Discussion : Scheduler Change (Message 6855)
Posted 27 Nov 2019 by Profile Laurence
Post:
I think I have found a solution. Please can you see if the settings work as expected. You should get the following:

Max 2 CPU, Max 1 Job => 2 threaded job 
Max 1 CPU, Max 2 Job => 2 single threaded jobs
18) Message boards : General Discussion : Scheduler Change (Message 6851)
Posted 26 Nov 2019 by Profile Laurence
Post:
(not sure where MAX_CPUS is set; looks like a global setting)

In the header file.

if (project_prefs.max_cpus) {
    if (n > project_prefs.max_cpus) {
        n = project_prefs.max_cpus;
    }

This code is here, without any doubt, but why here?
Guess a user wants to run 2-core ATLAS tasks and sets the web preferences to "2 CPUs".
This code will make every brand new 256-core-amdintel_ripper appear as a Fred Flintstone's 2 core machine.


These lines have now been deleted. Will look where they should be put.
19) Message boards : General Discussion : Scheduler Change (Message 6850)
Posted 26 Nov 2019 by Profile Laurence
Post:
Setting
Max # jobs 3
Max # CPUs 2

no app_config in use - I got a 3rd task and avg_ncpus stays 1, creating a single core VM.
Requesting new tasks, I get: lhcathome-dev 26 Nov 19:06:18 This computer has reached a limit on tasks in progress
When the max cpus was misused as task-limit you got 'No tasks available'

This is what I would expect for Theory as it is now a single core app. Try CMS which is multi-core.
20) Message boards : General Discussion : Scheduler Change (Message 6846)
Posted 26 Nov 2019 by Profile Laurence
Post:
I have disabled the Max # CPUs so setting it should have no affect.


Next 20


©2020 CERN