Development for LHC@home

Xsuite

Page 15: Avaiable on Boinc (Under study)

And source code is here

They released the 0.80 version of Xtrack.
Hope to see this app in our pcs

I'm sure Nvidia would love us all to buy NVIDIA TITAN V

---

Mad Scientist For Life

I'm sure Nvidia would love us all to buy NVIDIA TITAN V

I don't know if the new xtrack boinc app (if there is in the future), will use single or double precision.
A single precision app doesn't need top-level gpu.

Meantime, they released the new version 0.9.0

Meantime, they released the new version 0.9.0

New version, 0.10.0

I sure wish github didn't make me get an email code just to log in all the time

Are you working on the code of xtrack?
Meantime 0.10.1 is out

Meantime 0.10.1 is out

The new version, now, is 0.12.
And there is a new baby, XBoinc

New version is published, 0.14
And works on XBoinc.....maybe we will see a test app on our pc, before or later.

The new version is 0.15, but no news from boinc app

0.16.1 released

New version now is 0.18

Version 0.19.4 released

Version 0.21.0 released

New version, 0.23.1, with interesting news:

Introduce fcc-ee example

The new version is 0.26

Version 0.28 released

I was trying to solve Hyperthreading issue by playing with P and C states on this new (to me) Broadwell server and 38 of these picked this time to come to that computer.

So they were stressed tested as I finally had to restart the machine when boinc.exe stopped uploading.

Its back in non-hyperthreaded mode (need to update the BIOS) and they are running again.

5 things:

1) they do not use the BOINC checkpointing system properly. Under properties, they show no checkpoint since initial start time.
--- not sure if they saved any work since the initial 18 hours of run time (tell me if there is a way to check and if you need a copy of something).
2) they refused to respond to boinc.exe giving them the shutdown command. They got left as orphan processes after boinc.exe and rosetta WU's left RAM.
-- had to use Process Hacker to suspend then manually terminate the processes.
3) they are hardened against such abuse. Instead of 'computation error' upon restart of BOINC after computer rebooted, they started computing again.
-- maybe this is because they are starting fresh and have no data set to check for computation errors?
4) They start at 0% and 0 time; so if you are using a proprietary checkpointing scheme, it didn't update the BOINC client's progress status.
5) The machine is capped at 2MB d/l rate and it was hitting that cap for 30 minutes without d/ling new WU, was that these WU's in communication with the server?

Maybe these are all things known to the devs, but if I'm going to run test bed WU's, I should give you my report.

Aborted 5 to see the consequences. They did not get resent.

Running the other 33 till the deadline or they actually complete (unless you all tell me to end their run prematurely). I'll put off maintenance on that machine till they resolve.

.....
Maybe these are all things known to the devs, but if I'm going to run test bed WU's, I should give you my report.
Aborted 5 to see the consequences. They did not get resent.
Running the other 33 till the deadline or they actually complete (unless you all tell me to end their run prematurely). I'll put off maintenance on that machine till they resolve.

Seems that there are some works to do to the app...

While we are waiting for XBoinc app on our pcs, they release a new version of Xtrack, 0.29.4