1. 16 May, 2013 2 commits
  2. 15 May, 2013 3 commits
  3. 14 May, 2013 5 commits
  4. 13 May, 2013 4 commits
  5. 07 May, 2013 1 commit
  6. 03 May, 2013 2 commits
  7. 23 Apr, 2013 4 commits
  8. 18 Apr, 2013 1 commit
  9. 15 Apr, 2013 3 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)
    • 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
    • Pierre Cazenave's avatar
      Add the MIT licence · 0d3778ae
      Pierre Cazenave authored
  10. 08 Apr, 2013 2 commits
  11. 04 Apr, 2013 2 commits
  12. 03 Apr, 2013 1 commit
    • Pierre Cazenave's avatar
      Merge branch 'dev' · f3d36844
      Pierre Cazenave authored
      Bring in the changes from the dev branch into the master branch. These include:
      - Support for converting POLCOMS flow, index and grid files into the necessary files to write FVCOM river input files (NetCDF and nml files). The existing river functions have been updated to reflect the changes needed in the latest versions of FVCOM (3.1.x). write_FVCOM_river.m now uses the native MATLAB NetCDF routines to export to NetCDF.
      - Preliminary support for mean flow at the open boundaries. At the moment, the mean flow is interpolated from POLCOMS daily mean flow values. The necessary tools to write out the FVCOM ASCII mean flow files have been created, but I have not yet managed to successfully run a model with mean flow. Consider it a work in progress.
      - The NCEP surface forcing is now able to use either the MATLAB native support or otherwise (for older versions) the third-party OPeNDAP toolbox (http://www.opendap.org/pub/contributed/source/ml-toolbox/). It is still dependent on the air-sea toolbox (http://woodshole.er.usgs.gov/operations/sea-mat/air_sea-html/index.html). The surface forcing has had the sign convention fixed (see get_NCEP_forcing.m).
      - Vertical temperature and salinity profiles from POLCOMS model outputs are scaled to the FVCOM depth rather than truncating. Hopefully this means the full structure of the water column is preserved if POLCOMS and FVCOM differ in their depths (see get_POLCOMS_tsobc.m).
      - Export of the surface forcing can now use a precomputed surface heat flux rather than having to interpolate the four components only to merge them (see write_FVCOM_forcing.m).
      - Some of the older functions have been made more consistent in terms of the coding style (e.g. warnings are now turned on, or not turned off, for all functions). Similarly, the history global variable in any FVCOM NetCDF file now includes the name of the function from which it was generated.
      - The routine to replace variables within an FVCOM restart file now includes the ability to adjust the times for which the restart file is applicable. This is useful if you have a restart file for a model domain, but wish to use it for a different time.
      - A new function to reorganise open boundary elements to have an edge approximately normal to the open boundary has been added (fix_inside_boundary.m). The routine is somewhat brute force, and can result in invalid unstructured grids. As such, any changes should be reviewed in SMS prior to being used in a model run.
      - Additional tools (write_SMS_2dm.m and write_SMS_cst.m) provide functionality to export data from MATLAB to formats compatible with SMS.
  13. 27 Mar, 2013 2 commits
  14. 26 Mar, 2013 7 commits
  15. 19 Mar, 2013 1 commit