Hi,
unfortunately my applications do not switch anymore. I already edited the client_state.xml to reset long-term dept to 0.0 for all projects I run (SET@Home Enhanced, E@H, Climateprediction), but it still does not switch. for 2 days it runs exclusively E@H and since I edited the client_state.xml file this morning E@H again accumulated long term debt of -11000. What can I do to make it schedule correctly?
Configuration: BOINC 5.4.9 w/ trux calibrating 5.3.12tx36
E@H akosf U41.04,
SETI@Home Enhanced Crunch3r Windows 5.12_IPP_SSE3 w/ modified app_info.xml,
Climateprediction Standard.
When I pause E@H, Seti or Climateprediction will run but don't switch either.
I also see the exact same behaviour on both my Macs!
Thanks in advance!
Copyright © 2024 Einstein@Home. All rights reserved.
Problem with application switching
)
This doesn't explain your Mac problems but there have been incompatibility reports regarding Trux and BOINC 5.4.9. In fact, I couldn't get the two to work together at all - so I switched to the new client from Crunch3r. This post (and thread) at SETI has some discussion regarding the Trux problems.
I have seen the same issue on
)
I have seen the same issue on my linux box with Boinc clients 5.2.13 (vanilla and crunch3r optimised), 5.3.12tx36 of Trux between CPDN and SETI standard, i.e. pre-enhanced, optimised from crunch3r/naparst and before TMR. The only solution was to disable the 'leave applications in memory'switch for the boinc client (you can set this from your account page). Downside of this is that you loose any data that have been calculated between your last checkpoint and the moment ofthe switch. For Seti not an issue, for CPDN in my case (coupled models) approx 10 CPU minutes... I have bumped up the switch time from 60 to 120 minutes to reduce the impact of this, but still not very desirable.
Last week I switched to Seti enhanced (standard first) and upgraded Boinc to 5.4.9 (crunch3r). This proved to eliminate the switching issue. No clue why. Also the change of standard to optimised seti enhanced (5.12) did not change this.