1. 03 Jul, 2020 1 commit
  2. 24 Jun, 2020 2 commits
  3. 12 Jun, 2020 5 commits
  4. 11 Jun, 2020 1 commit
  5. 22 May, 2020 2 commits
  6. 23 Apr, 2020 1 commit
  7. 16 Apr, 2020 2 commits
  8. 06 Apr, 2020 1 commit
  9. 02 Apr, 2020 1 commit
  10. 31 Mar, 2020 1 commit
  11. 30 Mar, 2020 1 commit
  12. 27 Mar, 2020 2 commits
  13. 25 Mar, 2020 2 commits
  14. 20 Mar, 2020 1 commit
  15. 19 Mar, 2020 1 commit
  16. 18 Mar, 2020 1 commit
  17. 16 Mar, 2020 4 commits
  18. 13 Mar, 2020 1 commit
  19. 12 Mar, 2020 2 commits
  20. 11 Mar, 2020 4 commits
    • Ben Barton's avatar
      Moved preproc.Nest to grid.Nest · 7f2d2b03
      Ben Barton authored
      7f2d2b03
    • Ben Barton's avatar
      Nest is a subclass of OpenBoundary. · efe78190
      Ben Barton authored
      Nest._update_open_boundary() renamed to Nest._update_nest(). Updates to
      Nest.__init__(),  _update_nest() and add_nests() to accomadate the Nest
      structural changes. Nest.add_level() and Nest.add_weights() moved to _grid.OpenBoundary.add_nest_level() and _grid.OpenBoundary.add_nest_weights().
      efe78190
    • Ben Barton's avatar
    • Ben Barton's avatar
      Extra dev branch for re-structuring of Nest objects: · 81052434
      Ben Barton authored
      I've been working on setting up some boundaries and found that there is a lot
      of cross over in OpenBoundary and Nest objects. I found the structure of Nest
      confusing. Previously the structure was:
      model.open_boundaries[self.dims.open_boundary]
      model.nest[self.dims.open_boundary].boundaries[self.dims.nest_levels]
      It took a while to work out what the difference between Nest and OpenBoundary
      was especially because Model.nest is th shape of open_boundaries but without
      the attributes and Model.nest.boundaries does not corespond to open_boundaries
      but is actually the number of nest levels adjacent to the open_boundary.
      To clarify, OpenBoundary is the edge nodes with a single vertical depth level.
      I think it could be used for forcing FVCOM with just elevation. Nest has depth
      levels and adds nest levels which are the nodes horizontally connected to the
      respective OpenBoundary and help dampen u,v,t,s forcing at the boundary.
      
      The new structure will be:
      model.open_boundaries[self.dims.open_boundary]
      model.open_boundaries[self.dims.open_boundary].nest[self.dims.nest_levels]
      This means the required open_boundary can be indexed and then the list of
      optional nest levels associated with it can be indexed. The nests will not have
      boundaries at attributes and will instead have all attributes of OpenBoundary
      themselves with some extra attributes.
      
      This branch will have re-structuring and improvment to the documentation before
      being merged back into dev branch. Planned changes:
      - Nest will be a subclass of OpenBoundary as suggested in the the Nest TODO
      - OpenBoundary will be moved to preproc as suggested in the OpenBoundary TODO
      - add_level() will be made a function of OpenBoundary and renamed to
      add_nest_level()
      - add_weights() will be made a function of OpenBoundary and renamed to
      add_nest_weights()
      - Nest._update_open_boundaries() will be renamed _update_nest()
      - propagate changes to Model.add_nests() and hopefully other dependant
      functions
      81052434
  21. 06 Mar, 2020 3 commits
  22. 04 Mar, 2020 1 commit