1. 12 Jul, 2021 2 commits
  2. 21 May, 2021 2 commits
  3. 30 Apr, 2021 2 commits
  4. 16 Apr, 2021 2 commits
  5. 11 Jan, 2021 13 commits
  6. 02 Jun, 2020 1 commit
  7. 27 May, 2020 2 commits
    • Christopher Subich's avatar
      wave_reader: compute hill properly with z-decreasing · 4fba6227
      Christopher Subich authored
      Previously, wave_reader computed the hill height as a fixed
      
        zgrid(:,1,1) - MinZ // matlab notation
      
      which implicitly assumes that z increases along the third index.  If
      that assumption is violated, the BPE calculation breaks (in ways that
      can cause assertion failures based on roundoff error, at that).
      
      Fixing the calculation as min(zgrid(i,1,:)) at initialization time
      alleviates this problem.
      4fba6227
    • Christopher Subich's avatar
      wave_reader: allow FULL input types · 471ccd94
      Christopher Subich authored
      Previously, wave_reader locked 'FULL' (3D) input behind enabling
      restart.  This restriction was unnecessary, and doing so in fact made
      the specification of u/v/w/rho filenames useless.
      
      Deleting this check allows proper read-in of FULL datatypes, without
      faking a restart.  The only functional difference is that if
      perturbations are also enabled, they will be applied on top of the 3D
      data read.  This seems to be desirable, since it makes the application
      of the config-file settings more straightforward.
      471ccd94
  8. 04 May, 2020 1 commit
    • Christopher Subich's avatar
      Updates to solver parameters · 79b17389
      Christopher Subich authored
      Based on experience with a poorly-converging, steep hill case, the
      number of inner iterations in GMRES is increased to 40, and the number
      of outer iterations drops to 2.
      
      Please pay attention to GMRES warnings and report cases where things
      don't work well, there's probably an optimal parameter range (or else we
      could make the parameters a runtime config option).
      79b17389
  9. 10 Jun, 2019 1 commit
    • David Deepwell's avatar
      Fix topography error in wave_reader · 645e99d8
      David Deepwell authored
      The quadrature weights were found to be incorrect for mapped grids
      because they were adjusted using the topography which was not
      scaled properly. The topography needed to be adjusted to be relative
      of the 'minimum z-value'. This is in quation marks because it is
      not necessarily the absolute minimum, but rather the reference
      minimum.
      This shift also fixed the BPE calculation to have the same reference
      as the PE calculation.
      645e99d8
  10. 16 Apr, 2019 1 commit
  11. 02 Apr, 2019 2 commits
    • David Deepwell's avatar
      Fix error in tracer/rho safety dump in wave_reader · e5bec6c2
      David Deepwell authored
      The previous "fix" swapped rho and tracer.
      
      Update to version 2.0.4
      e5bec6c2
    • David Deepwell's avatar
      Add vortex stretching and enstrophy stretching production terms · a63ba535
      David Deepwell authored
      Vortex stretching is one of the dominant terms in both the
      vorticity equation and enstrophy equation. They also help in
      understanding the vortex dynamics and how energy at large scales
      cascades into small scales.
      
      The three components of vortex stretching (omega dot grad) u
      and the enstrophy stretching production (omega_i omega_j S_ij)
      are now included and can be computed with the derivatives
      case file. Files for vortex stretching terms are called
      vort-stretch<dim> where <dim> is one of x,y,z. The enstrophy
      stretching production file is called enst-stretch.
      
      As these quantities are the product of velocity gradients, care
      must be made to ensure adequate resolution is present.
      
      Update version to 2.0.3
      a63ba535
  12. 29 Mar, 2019 1 commit
  13. 26 Mar, 2019 1 commit
  14. 25 Mar, 2019 1 commit
  15. 22 Mar, 2019 6 commits
  16. 15 Mar, 2019 2 commits
    • David Deepwell's avatar
      Update Version message · 38d5d4ab
      David Deepwell authored
      The SPINS version is now the first thing printed in a simulation.
      Also fixed typo in writing the grid in BaseCase.cpp
      38d5d4ab
    • Benjamin Storer's avatar
      Adds version numbering to the repository · b6c48e5a
      Benjamin Storer authored
      The file VERSION now records the MAJOR_VERSION, MINOR_VERSION,
      and PATCH_VERSION.
      To update the version number, the user only needs to modify the
      appropriate lines in VERSION.
      
      Makefile has been updated to automatically pass the version
      information through compiler flags.
      
      BaseCase.cpp has been updated to add a print statement into the
      initialization function. By default, every casefile that uses
      BaseCase will now print the SPINS version with which is was compiled.
      This should help avoid issues with mis-matched versions.
      
      It will appear in the output as:
      SPINS Version 1.0.1
      
      The starting version is set to 2.0.0
      
      StackOverflow has a nice summary of when to change which version number
      (https://stackoverflow.com/questions/3826580/what-rules-does-software-version-numbering-follow)
       - Major version numbers change whenever there is some significant change
      being introduced. For example, a large or potentially
      backward-incompatible change to a software package.
       - Minor version numbers change when a new, minor feature is introduced or
      when a set of smaller features is rolled out.
       - Patch numbers change when a new build of the software is released to
      customers. This is normally for small bug-fixes or the like.
      b6c48e5a