1. 25 Jun, 2013 1 commit
  2. 24 Jun, 2013 2 commits
  3. 18 Jun, 2013 1 commit
  4. 17 Jun, 2013 1 commit
    • Pierre Cazenave's avatar
      Three main changes: · 38c1d574
      Pierre Cazenave authored
      1. Remove the pevpr data from the list of data to be retrieved (since
         it's not used in the calculations and it is only land-based anyway).
      2. Change the sign of the evaporation data (Et) to match the
         precipitation (FVCOM wants preciptation and evaporation to both have
         the same signs - ocean losing water is negative).
      3. Replace data outside the actual range with NaNs. This might cause
         some things to break later on (e.g. interpolation).
      38c1d574
  5. 06 Jun, 2013 3 commits
  6. 03 Jun, 2013 3 commits
    • Pierre Cazenave's avatar
      Flip the order of the vertical levels in the POLCOMS data to match its depth... · 4032b7ca
      Pierre Cazenave authored
      Flip the order of the vertical levels in the POLCOMS data to match its depth array values (i.e. go from the seabed to the surface instead of the other way around). This changes means the POLCOMS data matches the convention in the FVCOM arrays (where the surface is the first index) and in the POLCOMS depth data. Also change the 1D interpolation to use the pchip interpolation method (shape-preserving piecewise cubic interpolation) instead of linear interpolation. The original change from pchip to linear was because I thought pchip didn't do extrapolation, but since we're scaling the POLCOMS vertical profiles to the FVCOM depths, it doesn't matter. Finally, some miscellaneous changes (moving the creation of the open boundary nodes array to outside the loops and tidying up some of the whitespace/figures code
      4032b7ca
    • Pierre Cazenave's avatar
      Change the way the open boundary nodes are obtained to match that which is in... · a3c594dd
      Pierre Cazenave authored
      Change the way the open boundary nodes are obtained to match that which is in the code which generates Casename_obc.dat. This should stop problems with ordering values in the input arrays where the manner in which the list of open boundary nodes are generated in different ways resulting in different output orders
      a3c594dd
    • Pierre Cazenave's avatar
      Add a couple of diagnostic figures at the end of the function for sanity... · c1e071a9
      Pierre Cazenave authored
      Add a couple of diagnostic figures at the end of the function for sanity checking the function. Also change the way the open boundary nodes are index by using the same approach as is in the code to generate the Casename_obc.dat file. This should avoid problems where the interpolated arrays store the data in a different order from how FVCOM is expecting it (I am assuming here that FVCOM assumes the order of boundary nodes specified in Casename_obc.dat will be common across all input data which use the open boundary nodes. This seems sensible to me)
      c1e071a9
  7. 21 May, 2013 1 commit
    • Pierre Cazenave's avatar
      Add check to avoid setting nodes as river nodes when that node is part of only... · 3ea2af87
      Pierre Cazenave authored
      Add check to avoid setting nodes as river nodes when that node is part of only one element. If this is not added, then the model fills up the element without moving the water out of that element, eventually leading to a crash, which is obviously not ideal. The fix searches for another node in the element which is part of at least two elements, thereby avoiding the "element filling" issue
      3ea2af87
  8. 17 May, 2013 1 commit
  9. 16 May, 2013 4 commits
  10. 15 May, 2013 2 commits
  11. 14 May, 2013 4 commits
  12. 13 May, 2013 3 commits
  13. 07 May, 2013 1 commit
  14. 03 May, 2013 2 commits
  15. 23 Apr, 2013 2 commits
  16. 18 Apr, 2013 1 commit
  17. 15 Apr, 2013 2 commits
    • Pierre Cazenave's avatar
      This function has had the parts of the code which deal with loading the... · c6dcf62d
      Pierre Cazenave authored
      This function has had the parts of the code which deal with loading the discharge data and river positions farmed out into separate functions (get_POLCOMS_river_positions.m and get_POLCOMS_river_discharge.m). By removing that code from the function, this function can now focus entirely on finding the appropriate river node. The logic whereby nodes assigned multiple rivers have the discharge from those rivers summed remains (which differs from the now-extinct get_POLCOMS_rivers.m function which simply used the first river it came across and omitted any discharges from subsequent rivers)
      c6dcf62d
    • Pierre Cazenave's avatar
      Remove the original POLCOMS parsing script and replace it instead with two... · f2e5025a
      Pierre Cazenave authored
      Remove the original POLCOMS parsing script and replace it instead with two separate functions, one to get the positions and the other to import the discharge rates. The part of the original function responsible for finding suitable nodes and assigning the discharges has been moved into get_FVCOM_rivers.m. The reason for this separation of duties is to make each part more flexible. This approach means I can load my positions from a separate file whilst still using the POLCOMS discharge data. Once I have loaded those data, the function to find the suitable nodes is called separately. If you had an alternative source of data, then the latter function could still be used to find the nodes as all it needs is position information
      f2e5025a
  18. 08 Apr, 2013 1 commit
  19. 27 Mar, 2013 2 commits
  20. 26 Mar, 2013 3 commits