1) Message boards : Sixtrack Application : gFortran (Message 32409)
Posted 13 Sep 2017 by kyrsjo
GFortran is actually our main compiler, at least for the new (v4.6.30) executables. However we also support ifort and nag. Currently we're targeting Fortran2003, as it provides us with a lot of nice "modern" features like "retrieving the unit number of stdout/stderr"; the code is a mixture of Fixed-form (F77-style) and Free-form (F90 style) sources.

If you're interested in the code, please take a look at our GitHub repository:
Contributions are very welcome! :)
2) Message boards : Cafe LHC : ARM support (Message 30641)
Posted 5 Jun 2017 by kyrsjo
The test sixtrack version support aarch64, so it should work on raspberry pi 3.
3) Message boards : Sixtrack Application : AVX/AVX2 support (Message 30639)
Posted 5 Jun 2017 by kyrsjo
The test execs have and AVX version. From our initial testing there gain is rather small :( But let's see what happens when they are ran on more machines...
4) Message boards : Number crunching : SixTrack: Cross-OS validation = inconclusive results (Message 30633)
Posted 4 Jun 2017 by kyrsjo
Hi Kevin,

if you have some experience with Linux, you could try to build the executable + test harness locally and run through the tests?

To do that, clone the sources from GitHub:
then cd into the "SixTrack" subfolder, and run
./cmake_six BUILD_TESTING
This will make a new folder with the executable. You can the run the tests with
ctest -j 4
where I assumed that you want to run on 4 cores.
You can also run only the fast/medium/slow tests by adding the flag
-L fast
where you can replace fast with medium or slow.

If that all passes, the next step would be to build the real BOINC version; to do that first build the supporting libraries by running the "buildLibraries.sh" script, then build sixtrack as

FYI, you may have to install some libraries - especially some static libraries - to do these builds. It should be possible to "cheat" and do a dynamic build by adding "-STATIC" to the cmake_six command.
5) Questions and Answers : Unix/Linux : LHC@home sources available ? (Message 28966)
Posted 24 Feb 2017 by kyrsjo
I absolutely agree! Also, having the source open makes things easier for us too. We even had a bugfix from one of the volunteers :)

If you're interested in getting more involved, there will be a Google Summer Of Code project:
(scroll down for SixTrack)
6) Questions and Answers : Sixtrack : Very quick tasks - Six Track - Normal???? (Message 28957)
Posted 22 Feb 2017 by kyrsjo
Yeah, the goal of the SixTrack simulations is pretty much to find out how far out we can place the particles before they get lost by hitting the walls. This happens because at some amplitude, nonlinearities in the machine (magnet errors etc.) causes the particle amplitudes to grow exponentially. This is known as the "dynamic aperture" of the machine.

We can then study different optics settings, the effects of imperfections in the construction of the machine and in various equipment etc.
7) Questions and Answers : Sixtrack : Virtual box (Message 28956)
Posted 22 Feb 2017 by kyrsjo
SixTrack does not need virtualbox. There should be work...
8) Message boards : Sixtrack Application : Shiny new executables! Could you try them? (Message 28944)
Posted 21 Feb 2017 by kyrsjo
This is great news! Thank you so much for testing!

Looks like the other tests from the SixTest folder were happy as well:
(the two failed on Windows is a script to check consistency of the input files in the test suite, which doesn't really work on Windows. But as long as the test passes on UNIX, Windows is fine too). We didn't do a full test on BSD since essentially nothing changed there since the previous release.

I'll go and poke the guy who manages the submission system :)
9) Message boards : Sixtrack Application : Shiny new executables! Could you try them? (Message 28932)
Posted 20 Feb 2017 by kyrsjo
And we try again: https://github.com/SixTrack/SixTrack/releases/tag/v4.6.6
Note that there is a new version number - I cleaned up a few things in the build system (for UNIX too!) while I was at it.

It turned out that (a) I was linking the system libarchive, which WAS static except for linking the Windows system libraries, and (2) when I built my own libarchive, it picked up the dll for zlib istead of the .a, making it not fully static. The big problem is that when linking to a dll on windows, the function (as an example) "deflate" gets the symbol "__imp_deflate" instead of just "deflate" as when it is statically linked. Therefore I was not able to link my own self-built libarchive (at least not without needing a system zlib, which isn't generally present on a Windows system).

However, I managed to convince libarchive to link *statically* to zlib, so that I could do the same for SixTrack -> libarchive.

So unless there are other problems not yet seen, this should work.

Regarding mpr.dll, this is a standard Windows system library, present since XP:
I'm not sure why this gets linked - it could be from BOINC? However since this is a standard system library, present since the stone age, it shouldn't make any problems (famous last words).

The binaries are currently being tested on my workstation / under-desk electrical heater, and once they have passed + you confirm that XP works, we can push it to our test queue, then to production. We're getting there!
10) Message boards : Sixtrack Application : Shiny new executables! Could you try them? (Message 28924)
Posted 19 Feb 2017 by kyrsjo
I'll have a look at that; I normally just use the standard "ldd" tool that I know from Linux; but it seems that library loading on Windows is a bit more convoluted than on Linux.
11) Message boards : Sixtrack Application : Shiny new executables! Could you try them? (Message 28915)
Posted 18 Feb 2017 by kyrsjo
Good to hear! The Linux execs were compiled on a 32-bit VM with fedora 25, so pretty much native.

In general we've had much less problems with building up the *NIX execs. I really need to figure out whats going on with libarchive on Windows on Monday :/
12) Message boards : Sixtrack Application : Shiny new executables! Could you try them? (Message 28907)
Posted 17 Feb 2017 by kyrsjo
Hi all, sorry for yet another delay - boinc127 identified one problem, problem number 2 was that on Windows, I was linking the *system* libarchive, which on MSYS/CYGWIN32 was again linking BCrypt (dynamically); not my carefully stripped-down version.

I fixed that too, but now there is some unnamed library it can't find... Will look more on monday. Worklog is in the issue tracker:

Regarding keeping an old WinXP build machine around, we tried, but IT would not let us... :( I can understand why though :)
13) Message boards : Sixtrack Application : Shiny new executables! Could you try them? (Message 28902)
Posted 17 Feb 2017 by kyrsjo
Hmm, I wrote that code some weeks ago :)

So.. LibArchive is (no longer) linking to BCrypt, we are manually forcing SixTrack to link to BCrypt. The reason is that when I wrote this, LibArchive on Windows required BCrypt, so to link to LibArchive, I needed to link to BCrypt.

Removing that dependency should fix it. I'll try to push a new executable around 5-ish today!
14) Message boards : Sixtrack Application : Shiny new executables! Could you try them? (Message 28894)
Posted 16 Feb 2017 by kyrsjo
Great, but don't thank me, thank James:

FYI, I'm a bit lost for what to do with the WinXP problem; it seems to be some kind of bug in libarchive's cmake build system. I did try to fix it in this pull request:
which is where the second set of Windows binaries came from. It didn't help tough :(

If someone have suggestions for how to fix this (or patches to LibArchive...), I'm all ears!

Otherwise, I'm very happy to hear that the binaries seem to work on everything but Windows XP! If we can fix that, we will; if not I fear we will have to do without it...

On our end, we're waiting for the guy who runs the BOINC server to get back from holidays (which will happen next week), so that we can push out the new binaries. So soon.
15) Message boards : Sixtrack Application : Shiny new executables! Could you try them? (Message 28891)
Posted 15 Feb 2017 by kyrsjo
To check the contents, use "diff", as in "diff fma_sixtrack fma_sixtrack.canonical" :) If it returns nothing, then everything is great.

If one of the files have windows line endings and the other not, diff will claim they are different. To make diff ignore those, add the flag "--strip-trailing-cr".

For a graphical diff, install "meld" from your distributions repos.
16) Message boards : Sixtrack Application : Shiny new executables! Could you try them? (Message 28872)
Posted 14 Feb 2017 by kyrsjo
New windows execs:

I'm not 100% sure if they are free of the bcrypt dependency tough; I did try to disable it but LDD tells me something is still linking it. Could you please try?
17) Message boards : Sixtrack Application : Shiny new executables! Could you try them? (Message 28865)
Posted 14 Feb 2017 by kyrsjo
Thanks a lot!

I feared something like this on XP. The issue is that a library we use to interact with .zip files, "libarchive", links dynamically to bcrypt and a few other system libraries on Windows, and there seems to be no way to link statically with system libraries on Windows. However looking into the CMakelist for Libarchive https://github.com/libarchive/libarchive/blob/master/CMakeLists.txt, it seems that I can disable "Crypto New Generation" https://msdn.microsoft.com/en-us/library/windows/desktop/aa376210(v=vs.85).aspx support when compiling Libarchive and it should not try to link with BCrypt... And since we anyway don't need encrypted .zip's, disabling this feature should not be any problem (and if we would have needed the feature, I could probably get libarchive to use openssl on Windows also).

I'll try make and publish a new set of Windows execs later today, without this "feature"!
18) Message boards : Sixtrack Application : Shiny new executables! Could you try them? (Message 28855)
Posted 13 Feb 2017 by kyrsjo
Great! I don't know why something was wrong, and I don't know what you mean with multivolume.

However when I go to the link https://github.com/SixTrack/SixTrack/tree/master/SixTest/fma and click on the "Sixin.zip", I get to https://github.com/SixTrack/SixTrack/blob/master/SixTest/fma/Sixin.zip (i.e. "blob") where I can click on the "download" or "view raw", both which fetches the .zip.

Maybe you downloaded the webpage or something? Anyway, great that it works, and sorry that my instructions were not 100% clear!

346869 bytes is correct, this is the same as I get on my dev machine:
fma $ ll Sixin.zip
-rw-rw-r--. 1 kyrsjo kyrsjo 346869 Feb 9 12:09 Sixin.zip

Thanks again!

And if anyone has a WinXP machine, that would be absolutely fantastic... The oldest I have is 2008 Server, which *should* be equivalent, but one never knows. Old OS X and old non-redhat Linux would also be nice...
19) Message boards : Sixtrack Application : Shiny new executables! Could you try them? (Message 28853)
Posted 13 Feb 2017 by kyrsjo
I'm pretty sure this error is due to a corrupt Sixin.zip; I was able to reproduce it only by puting "asdf" in the header of the .zip file... Could you try to redownload?

If you open the .zip file with "more" from the console, it should look something like this:
20) Message boards : Sixtrack Application : Shiny new executables! Could you try them? (Message 28852)
Posted 13 Feb 2017 by kyrsjo
Dear Crystal Pellet,

thanks a lot for trying it, stuff like this ( executable compatibility for systems that I don't have access to) is exactly what I'm trying to catch here!

At least the executable ran; however it seems that it could not read the Sixin.zip (it did find the file tough...). Hmm, strange?

Just to double-check that we're running it in the same way:
1) create an empty folder "test" under C:\Users\USERNAME\ (where my username has no spaces in case that matters
2) Download the .exe and move it into that folder
3) Download the .zip by clicking the "Download" button here: https://github.com/SixTrack/SixTrack/blob/master/SixTest/fma/Sixin.zip
4) Move the .zip into that folder too - do NOT unpack it or alter it in any way.
5) Open a windows console (CMD)
6) cd test
7) SixTrack_465_libarchive_cr_boinc_api_crlibm_fast_tilt_cmake_Windows_gfortran.exe_static_AMD64_32bit
(like you did)

... wait ...

8) more fma_sixtrack

lots of stuff like this:

9) more fort.6

lots of stuff like this:


If you have access to an md5sum utility, the sum should read like this:

eaa3679611085da29bea20137be232cf Sixin.zip

Next 20

©2023 CERN