1) Message boards : News : The SixTrack team welcomes the LHC@Home volunteers at the CERN open days (Message 39940)
Posted 16 Sep 2019 by Eric Mcintosh
Post:
Hi Eddie, our presentations are coming. I am making a big
effort on our WWW pages.
GPUs.....we can run, but I'll expand on this later.
Old GPU's are not IEEE 754. The memory requirement becomes
large, as do the sizes of the result files.

Thanks for your support.. Eric
2) Message boards : News : The SixTrack team welcomes the LHC@Home volunteers at the CERN open days (Message 39939)
Posted 16 Sep 2019 by Eric Mcintosh
Post:
Hi Nicholas, I'm a bit late too tell you where.
Many many people had difficulty finding us, and not just us.
There was a crazy system of naming ME23, ME15, etc etc.
You needed a smart phone to have any chance. I am
complaining to organisers, why was there NO MAP!
We had only half the volunteers expected on Saturday,
around 10, and 3 on Sunday. Never mind we shall shortly
post our presentations on the WWW with links from here, the MBs.

Yes, your CPU will get hot. SixTrack is CPU intensive. Many systems
throttle back the CPU(s) when the temperature rises.

Thanks for your support. Eric
3) Message boards : Sixtrack Application : SIXTRACKTEST (Message 39914)
Posted 13 Sep 2019 by Eric Mcintosh
Post:
Thanks, excellent feedback. Memory requirement could be reduced
by tracking fewer particles in the task. Memory management in SixTrack
is now dynamic. There must be something wrong with our memory estimate
I think. In the first place we should avoid using all your memory and a
potential deadlock........We shall see. Eric.
4) Message boards : Sixtrack Application : Inconclusive results (Message 39766)
Posted 30 Aug 2019 by Eric Mcintosh
Post:
Hi Stick, yes this is a real pain in the neck. Seen it often.
Maybe our support can improve this after other really major
scheduling and task distribution are solved. Apologies. Eric
5) Message boards : Cafe LHC : McIntosh (Eric) is back (Message 39733)
Posted 25 Aug 2019 by Eric Mcintosh
Post:
Dear All, thank you for your messages and for all the encouragement.
As I said, I shall be at the CERN Open Days, 14th and 15th September,
and hope to make or renew some personal contacts. In the meantime,
I am hoping IT can resolve the database issues as we have lots of work
to run. Eric
6) Message boards : LHC@home Science : CERN Open days 2019 (Message 39730)
Posted 25 Aug 2019 by Eric Mcintosh
Post:
God Willing Weather Permitting, I shall be there, and looking
forward to meeting you. Eric.
7) Message boards : Cafe LHC : McIntosh (Eric) is back (Message 39693)
Posted 23 Aug 2019 by Eric Mcintosh
Post:
After various problems and some major heart surgery I am back in business.
I shall be confining myself to writing THE paper on result reproducibility,
but still keeping an eye on LHC@home and in particular on invalid results
or validation failures. My (young :-) colleagues have done a fantastic job
on SixTrack during my absence. It is now almost Fortran 2008, much more
modular and a great deal of new functionality. We are exploring the
possibility of performing ten million turns, but with the work split into batches
of say one hundred thousand turns. There is a big question here about the
amount of network activity required, as against the length of the task.
That's it for now, more news in the SixTrack thread whenever. Eric
8) Message boards : LHC@home Science : CERN Open days 2019 (Message 39155)
Posted 20 Jun 2019 by Eric Mcintosh
Post:
CERN Open Days 2019 | 14–15 September (early heads up)
On 14 and 15 September 2019, CERN will open its doors to the public for two special days at the heart of one of the world’s largest particle-physics laboratories.

The CERN Open Days have become a regular feature of the period that we call the “long shutdown” during which our accelerators stop for around two years, to benefit from upgrades and renovation work. We are now in Long Shutdown 2.

The 2019 Open Days will give visitors the chance to discover our facilities, both underground and on the surface. With free admission to debates, film screenings, theatre performances, experimental workshops and dozens of visit points spread all over the site, we will take you to the heart of our Laboratory, in direct contact with the science of today and tomorrow.
9) Message boards : Sixtrack Application : Errors on sixtrack tasks (Message 32642)
Posted 6 Oct 2017 by Eric Mcintosh
Post:
OK, thanks again. James has deleted the erroneous tasks. Eric.
10) Message boards : Sixtrack Application : Errors on sixtrack tasks (Message 32636)
Posted 5 Oct 2017 by Eric Mcintosh
Post:
Thanks Harri; looks like a genuine "physics" problem.....
I shall be seeing James, the user, today I hope. Eric.
11) Message boards : Sixtrack Application : SIXTRACKTEST (Message 32591)
Posted 2 Oct 2017 by Eric Mcintosh
Post:
Hi, it is dear to my heart to be as inclusive as possible.
I'll see if I can build on an old Linux system of mine,
and especially for my "dear old" 32-bit systems.
No promises, but I should have news in a week or so.
(There might be compiler problems/bugs on these ancient
platforms. I am aware of the horrible bind between new hardware
requiring new software and new software requiring new hardware!
I am against the "throw away" culture to the limits of
the possible.) . Eric.
12) Message boards : Sixtrack Application : More Work (Message 32589)
Posted 2 Oct 2017 by Eric Mcintosh
Post:
I'll try and find out. I'll be putting more work but I need to sort out
the new procedures for running specific cases and for getting
back all the result files before running more and longer cases.
Hopefully only a few days.
Eric.
13) Message boards : Sixtrack Application : More Work (Message 32500)
Posted 22 Sep 2017 by Eric Mcintosh
Post:
Well, I have painfully managed to download all existing results
and I am now submitting more work as best I can.

The new executables look very good from the CERN side, but since
Invalid and other failed results are now deleted I have a problem in
analysing these errors since the results never reach me.

I shall be trying to use the validator log in the meantime.
Shame as the new execs return the stderr which is a big help.

Eric.
14) Message boards : Sixtrack Application : More Work (Message 32498)
Posted 22 Sep 2017 by Eric Mcintosh
Post:
I am trying but the CERN file system keeps killing my procedures! Eric.
15) Message boards : Sixtrack Application : More Work (Message 32479)
Posted 20 Sep 2017 by Eric Mcintosh
Post:
New work is being submitted and appears to be taken! Eric 12:28 CST
16) Message boards : Sixtrack Application : More Work (Message 32478)
Posted 20 Sep 2017 by Eric Mcintosh
Post:
I am trying to submit new work, but there seems to be a network/AFS/CERN
service problem. More work as soon as possible.

Work has been pulled because of some of it was incorrect due to changes
required by the new SixTrack executable in the BEAM block of fort.3 input.
The tasks I know about all had names beginning Jone.....but that was only
about 3,500 and I deleted the WUs.

More news soonest. Eric.
17) Message boards : Sixtrack Application : Sixtrack tasks with name starting with Jone0_sep_jta_bbo are crashing on my system (Message 32461)
Posted 18 Sep 2017 by Eric Mcintosh
Post:
Dear All, apologies for the "bad" WUs. I have tried to delete them myself.
Eric.

Well I have tried to delete all the "bad" Jone
WUs. I might even have succeeded. I can do
no more for now. Kyrre should please check the
BEAM block and let Dobrin know. It looks
wrong to me with 7 items when only 4 or 5
are expected........

MYSQL does not like an "_" in the names! It has
a special significance. (I'll now have to print
another giant manual for MYSQL.) The boinc
ops facility for deleting WUs then fails because
of the "_"s in the WU name.

Luckily it turns out that just "Jone" and not "Jone_"
was sufficient to select the WUs.

Afrer double_checking I see all such Jone WUs have
server_state 5 which means "OVER" although some
have (of course) outcome 4 "IN PROGRESS".

I think that means they will be deleted in the normal way.
18) Message boards : Sixtrack Application : Sixtrack tasks with name starting with Jone0_sep_jta_bbo are crashing on my system (Message 32460)
Posted 18 Sep 2017 by Eric Mcintosh
Post:
Thanks a lot; chasing it with colleagues.
Either a bug in new SixTrack or a user error. Eric.



+1
https://lhcathome.cern.ch/lhcathome/result.php?resultid=157112455
19) Message boards : Sixtrack Application : 260.000 WUs to send, but no handed out (Message 32451)
Posted 17 Sep 2017 by Eric Mcintosh
Post:
There is a major problem with the distribution of tasks (dating from the
integration of the other projects with SixTrack). I myself am suffering
like you. My 4 processor Windows 10 couldn't get work either. I tried
reset, tried a re-install of the BOINC manager, etc and finally I got 100
Tasks! I was now using the client defaults, although I normally don't
cache tasks. So it seems you either get no tasks or too many. The problem
is being looked at but no solution seems to be available. I agree the
VirtualBox message is annoying but the IT emphasis is on trying to
get more clients running for the other sub-projects. In addition the
BOINC project management pages are so slow to access, several
minutes for each click, as to be unusable. This makes it very difficult for
me to follow up on other problems. I think we still have some HyperThreading/
BIOS problem, process creation failing on Windows, tasks not being
distributed. The slow start up on Windows 10 seems to be solved with the
new executables, which seem to be running well. The overall error rate
is down to about 2.5%, but we can do better.
Apologies and I await action from support. Eric.
20) Message boards : Sixtrack Application : "SixTrack Tasks NOT being distributed (Message 31900)
Posted 9 Aug 2017 by Eric Mcintosh
Post:
Sorry I can'h help with this. I'll pass it on.
(We have been having upload, even download, problems for quite
some time now, like years! I have made many suggestions but await a fix.)

Maybe you could turn on some file transfer debug options for the
event log and send it to eric.mcintosh@cern.ch. Eric.

This WU say uploading, but don't do this:

https://lhcathome.cern.ch/lhcathome/result.php?resultid=153142268

Have someone more possibility to see whats wrong?


Next 20


©2019 CERN