Skip to content
Snippets Groups Projects
  1. Sep 02, 2021
    • Christopher Subich's avatar
      Update dependencies to Blitz 1.0.2 and update to new MPI standard · 937c04ae
      Christopher Subich authored
      This commit updates make_deps.sh to build newer versions of Blitz (1.0)
      and fftw (3.3.9).  The 2010 version of Blitz no longer builds with the
      newest versions of GCC, and there is no harm in updating FFTW.
      
      The newest versions of Blitz (github head) require cmake to
      build, and some systems still in use have old, incompatible versions of
      cmake.  Blitz 1.0.2 requires python to complete its build process (some
      files are auto-generated).
      
      The new version of Blitz dropped the blitz::Vector type, being
      equivalent to a 1-dimensional array, so it was replaced with
      blitz::Array<type,1> instead.
      
      Additionally, the Parformer (parallel transpose) code was adjusted to no
      longer use MPI_UB to define the upper bound of the array section
      datatype.  MPI_UB was deprecated in the MPI-2 standard and removed in
      the MPI-3 standard, so SPINS could fail to build with some new MPI
      libraries (OpenMPI 4.0.3 is confirmed to break).
      
      Because this commit updates dependencies, the patch version is
      incremented.
      937c04ae
  2. Jul 30, 2012
    • Christopher Subich's avatar
      Initial commit · 58fbdb5d
      Christopher Subich authored
      This is the initial commit of SPINS to a git repository, coming from
      an essentially unmanaged environment.  While this is a *complete*
      archive, this is probably not the most useful form for development
      going forward.  Notably, the future management should be:
      
      1) Pare down the case files
      
      2) Establish branches for individual users.  Not as a long-term goal,
         but instead to keep user-specific case files from lingering in
         the main repository long after their use is obsolete.
      
      2b) Establish semipermanent branches for typical users.  A release
         branch should include the basic documentation cases, a benchmark
         case should include benchmarking cases, and there are probably
         others that aren't coming to mind now.
      
      3) Add helpful MATLAB processing scripts to the repository.  Too
         much of that is ad-hoc now, completely unmanaged.
      
      4) For papers/etc, establish tagged versions.
      58fbdb5d
Loading