1. 23 Apr, 2019 1 commit
  2. 05 Apr, 2019 2 commits
  3. 04 Apr, 2019 2 commits
  4. 02 Apr, 2019 4 commits
  5. 01 Apr, 2019 1 commit
  6. 26 Mar, 2019 3 commits
    • Enrico Bothmann's avatar
      Add --enable-analysis to GitLab CI · b42d5aab
      Enrico Bothmann authored
      This gives better code coverage in test builds. This is now possible
      because the timeout for the project CI has been increased.
      We also reduced the number of parallel builds to 4, since we got
      "virtual memory exhausted" messages in our CI builds.
    • Enrico Bothmann's avatar
      Replace C++ MPI bindings with C MPI bindings · f4e3273e
      Enrico Bothmann authored
      The C++ MPI bindings have been deprecated a long time ago and are e.g.
      not enabled per default in OpenMPI 4 (or even present, since I found the
      open-mpi configure flag to be defunct for me). Custom wrapper functions
      are now defined in My_MPI class.
    • Enrico Bothmann's avatar
      Remove obsolete Exception_Handler files · dd42d720
      Enrico Bothmann authored
      The Exception_Handler was superseded by Terminator_Objects in
      1a1de05a. The files were removed from the Makefile.am sources list but
      not removed from the repo.
  7. 21 Mar, 2019 1 commit
  8. 18 Mar, 2019 1 commit
  9. 11 Mar, 2019 1 commit
  10. 08 Mar, 2019 3 commits
  11. 07 Mar, 2019 1 commit
  12. 06 Mar, 2019 3 commits
  13. 20 Feb, 2019 1 commit
  14. 15 Feb, 2019 3 commits
  15. 14 Feb, 2019 1 commit
  16. 12 Feb, 2019 1 commit
  17. 11 Feb, 2019 3 commits
  18. 04 Feb, 2019 1 commit
  19. 24 Jan, 2019 2 commits
    • Enrico Bothmann's avatar
      Fix YAML syntax in LHC_Tops example · 4143fa86
      Enrico Bothmann authored
      ... and remove the outdated LOOSE_METS tag, which leads to yet another
      crash. In addition, clean up the syntax in the Tops_plus_* examples.
      Lastly, remove obsolete (and possibly problematic?) semicolons after
      SCALES specifications.
    • Enrico Bothmann's avatar
      Rewrite settings input using YAML · eb96f45c
      Enrico Bothmann authored
      This commit closes #10.
      - Replace custom configuration parsing and format with a YAML-based
      - Improve implementation of settings handling to enable features such
        - Generally only specify defaults once in the code, not scattered
          throughout with possibly different values
        - Print comprehensive report of values used for each setting at the
          end of a run
        - Warn when a setting is specified that is not used during a run (this
          is foreseen and now possible, but not implemented yet)
      NOTE: This is a squashed commit to keep the commit history of master
      simple. The full history of the development branch will be retained as
      10-rewrite-settings-input+commit-history in case it is needed, e.g. to
      find a (small) changeset that introduced a bug using git-bisect.
      A good example for new syntax is:
      The command line can process words using the YAML syntax, but also
      supports the old legacy syntax, at least for scalar settings.
      In the code, setting default settings and getting the resolved value
      for a setting can be done e.g. as follows:
      auto hds = Settings::GetMainSettings()["HARD_DECAYS"];
      const auto apply_br
        = hds["Apply_Branching_Ratios"].SetDefault(true).Get<bool>();
      Note also that Sherpa can now process several configuration files:
      `Sherpa "RUNDATA: [1.yaml, 2.yaml, ...]"`, with settings in files to the
      right taking precedence over settings in files to the left. This can be
      useful for specifying base set-ups and then deriving specialisations.
      A more detailed discussion of the new settings architecture is given
      (accessing this link might require developer access to the repository).
      Lastly, note that physics results are guaranteed to stay the same after
      this commit. If you find that to be not true, please contact me. When
      soft physics is used, numerics sometimes causes the statistics not to be
      the same after this commit. However, I've got some patches to mitigate
      this to some degree. So in any case, contact me if you find differences
      between results generated with this commit and the preceding one.
  20. 23 Jan, 2019 1 commit
  21. 22 Jan, 2019 2 commits
  22. 21 Jan, 2019 2 commits