|
21)
Message boards :
Sixtrack Application :
Shiny new executables! Could you try them?
(Message 28850)
Posted 13 Feb 2017 by kyrsjo Post: MD5SUMs should be:
|
|
22)
Message boards :
Sixtrack Application :
Shiny new executables! Could you try them?
(Message 28849)
Posted 13 Feb 2017 by kyrsjo Post: Hi all, we've made some shiny new executables that will soon be pushed out (first to more testing with actual BOINC, then to actual BOINC): https://github.com/SixTrack/SixTrack/releases/tag/v4.6.5 These are execs for Linux (32- and 64-bit), Windows(32- and 64-bit), OS X (Darwin, 64-bit), NetBSD (64-bit) and FreeBSD(64-bit). They pass all tests on our systems; however if you have the chance to try and run them on yours, that would be fantastic - especially if you have an old (Win XP?) and/or actual 32-bit systems hanging around. The best way to try them would be to run it in a folder with the "Sixin.zip" from this folder: https://github.com/SixTrack/SixTrack/tree/master/SixTest/fma I.e. put the Sixin.zip (Don't uncompress it!) together with the Sixtrack binary in an empty folder, open a terminal in that folder, and run SixTrack. This tests produces quite a bit of output (over several files, so run it in a "fresh" folder), and should take about 30 minutes to run. The actual "terminal" output should go to the file "fort.6". After it finishes, take a look at the file "fma_sixtrack". This should be the same as the file "fma_sixtrack.canonical" in the github repository (possibly excluding the Windows line-endings if you ran it on a Windows machine). If you do this, please leave a post with how it went (success/failure), which OS/distro and CPU architecture. Especially if something crashes, please let us know! Kyrre Sjobak, SixTrack developer@CERN |
|
23)
Message boards :
Sixtrack Application :
MacOS executable
(Message 28800)
Posted 6 Feb 2017 by kyrsjo Post: Ah, Theory tasks, not SixTrack. Have you asked in their forum? |
|
24)
Message boards :
Sixtrack Application :
MacOS executable
(Message 28795)
Posted 6 Feb 2017 by kyrsjo Post: Kernel panic? That's crazy! Configuration? And yes, I think we'll release a 32-bit Linux version. However when I tried to build it, I found that the flag in BOINC for compiling a 32-bit Linux version on 64-bit Linux (--with-boinc-alt-platform=NAME) does exactly nothing. :/ So I guess I have to get a 32-bit Linux VM then... https://boinc.berkeley.edu/trac/wiki/BuildSystem |
|
25)
Message boards :
Sixtrack Application :
i686 instead of x86_64: why?
(Message 28793)
Posted 6 Feb 2017 by kyrsjo Post: AFAIK the 64-bit binaries are actually 32-bit, just renamed. Take a look with "file" command: sixtrack_lin32_4517_pni.linux: ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, for GNU/Linux 2.6.18, BuildID[sha1]=b42e105d3abfa5c510f49b725ce1647140763030, not stripped sixtrack_lin32_4517_sse2.linux: ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, for GNU/Linux 2.6.18, BuildID[sha1]=f421c2e66bd497329337d2e2d49f409753df4e51, not stripped sixtrack_lin64_4517_pni.linux: ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, for GNU/Linux 2.6.18, BuildID[sha1]=b42e105d3abfa5c510f49b725ce1647140763030, not stripped sixtrack_lin64_4517_sse2.linux: ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, for GNU/Linux 2.6.18, BuildID[sha1]=f421c2e66bd497329337d2e2d49f409753df4e51, not stripped |
|
26)
Message boards :
Sixtrack Application :
MacOS executable
(Message 28767)
Posted 2 Feb 2017 by kyrsjo Post: The problem is when BOINC tries to validate results from SixTrack 4.5.30 (Mac OS) with results from 4.5.17 (everything else); they are not always *exactly* the same due to numerical roundoff, so BOINC will mark them as invalid. I don't know what can be done about those WUs... As I said, they might have passed if compared to another mac result. How does this affect your scores (I'm new to BOINC...)? From the scientific perspective, it is very good that if they DO pass the validation test, the physics is OK, so we don't need to go hunt down every WU that was done and validated on OS X and then resubmit these. As far as I know, the main thing remaining before we can release 4.6 is to fix the testing code on Windows, so that we can validate that our Windows executable produces the correct results. Then we need to run the tests, and hopefully that's it... Again, thanks a lot to those of you who pointed this out! |
|
27)
Message boards :
Sixtrack Application :
MacOS executable
(Message 28763)
Posted 2 Feb 2017 by kyrsjo Post: FYI: The macOS results (from SixTrack version 4.5.30) are physically valid since none of the currently running inputs use the removed RIPP feature, however they may differ slightly from the Linux and Windows version (from SixTrack 4.5.17) as in version 4.5.25 we fixed a small bug in how the input files were read. This means that when it compares results from MacOS with Windows or Linux, it fails... We're really sorry for this mess. The good news is that version 4.6.x is in the final stages of testing, introducing lots of new features for the researchers running the simulations, and versions for Linux (64-bit, we can probably do 32-bit as well if there is demand for it), Mac OS, Windows (64- and 32-bit), FreeBSD and possibly NetBSD. AVX is also supported, and we've also acquired an ARM server to test on... Further we think we've figured out why it is sometimes driving the I/O crazy (overzealous flushing of output files) - fixing this should speed things up quite a bit. So there may be another release not so long after the next one. Now why it hasn't stopped sending SixTrack jobs to Mac hosts I unfortunately cannot answer; my work is mainly on the SixTrack application programming side, not on the job management code. However I know it is being looked into. It is possible to follow the development at our GitHub page: https://github.com/SixTrack/SixTrack Please let us know if you see something strange :) There is also a Google summer of code internship coming up... Thanks a lot for your computing time and patience, it is really appreciated! -- Kyrre Sjobak, SixTrack developer @ CERN |
|
28)
Questions and Answers :
Unix/Linux :
LHC@home sources available ?
(Message 28660)
Posted 25 Jan 2017 by kyrsjo Post: I know this is an ancient post, however, the sources can be found here: https://github.com/SixTrack/SixTrack |
|
29)
Questions and Answers :
Unix/Linux :
FreeBSD port
(Message 28659)
Posted 25 Jan 2017 by kyrsjo Post: Cool that people are interested in a FreeBSD port! I know one of the SixTrack developers was looking into it yesterday, I'll forward him this thread - it might actually not be that hard to do... Regarding the compiler, we can actually compile with either gfortran, ifort, or nagfor on the Fortran side; and either gcc, icc, or clang on the C side. The problem is not compiling SixTrack itself, but rather to compile and link BOINC's zip libraries on Windows with Mingw on MSYS2. Which is why we're now pushing to use libarchive for that functionality. If you're interested in the code, see https://github.com/SixTrack/SixTrack/issues/39 and https://github.com/SixTrack/SixTrack/pull/173 --- Kyrre, SixTrack developer. |
Previous 20
©2024 CERN