Messages

Milkyway @ home is mainly multithreaded.

The numbers in brackets indicate less than 100% of 4 threads in use.  The correct answer should be 82%, by calculating (CPU time / wall time / CPU threads) * 100

I think what you might have done is forget to divide by the CPU threads, which gives 328%, which was then capped at 100%.

Thanks, I keep forgetting to look down there.  Although you do seem to duplicate these in the right click context menu, perhaps you should add detach?

I cannot find a way to detach a project, I expected it in the context menu when I right click a project in the projects tab.

But on the phone I can change battery percentage to crunch at, why is it not displayed in boinctasks.js?

I cannot change for example the minimum battery level in here.

I just shoved that in because the CPU isn't needed for a lot of maths apps, the GPU handles it itself, and I don't think Boinc would accept "0".  So would 0.01 be "nicer"?

Thanks for all your effort, Boinc is horrid without Boinctasks!

I'd donate but I don't have spare cash.

Boinc seems to work with this number, and your original Boinctasks displayed the 0.001 correctly.

When I go to the tasks tab, and sort by project name, the projects beginning with a capital letter are listed first.

Currently I have to go into the projects tab and right click LHC to get to their website, in the original Boinctasks, I could right click a task of theirs.

I miss the 2h (1h33) in the elapsed column in Boinctasks original.  I can't find a way to add the actual CPU time in brackets, I just see the wall time.  I assume Boinctasks.js can see it, as it's using it to calculate the CPU column as a percentage.

    <app>
        <name>ap26</name>
        <max_concurrent>0</max_concurrent>
        <gpu_versions>
            <gpu_usage>0.330000</gpu_usage>
            <cpu_usage>0.001000</cpu_usage>
        </gpu_versions>
        <fraction_done_exact>1</fraction_done_exact>
        <report_results_immediately>0</report_results_immediately>
    </app>

Results in:

By "very dangerous" I assume you mean users lose work by mistake?

Sorry to waste your time, I should have mentioned dark mode!

I take it 2.7 is in the works as my 2.6.2 says up to date.