1. 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.
      f3d36844
  2. 27 Mar, 2013 2 commits
  3. 26 Mar, 2013 7 commits
  4. 19 Mar, 2013 1 commit
  5. 18 Mar, 2013 2 commits
  6. 15 Mar, 2013 4 commits
  7. 13 Mar, 2013 3 commits
  8. 12 Mar, 2013 3 commits
  9. 11 Mar, 2013 3 commits
  10. 01 Mar, 2013 1 commit
  11. 28 Feb, 2013 7 commits
  12. 27 Feb, 2013 2 commits
    • Pierre Cazenave's avatar
      Big changes here: · 85154e0b
      Pierre Cazenave authored
      1. Do the vertical interpolation of the u and v components separately then at the end calculate the depth averaged velocity as well as the depth averaged u and v components into separate fields in Mobj. This is all necessary for outputting the ASCII files for mean flow and the open boundaries.
      
      2. Make the vertical interpolation scale the POLCOMS-ERSEM depth range to match the current FVCOM node's depth range, thus squeezing or stretching the vertical velocity profiles into the FVCOM depth.
      
      3. Add a commented out section which can be used to plot the vertical profiles to make sure they have interpolated correctly.
      85154e0b
    • Pierre Cazenave's avatar
      Two things: · 7b3cfce0
      Pierre Cazenave authored
      1. Remove the totally unnecessary loop iterating through the vertical levels on the vertical interpolation secion. No idea what that was doing there.
      
      2. Change the interpolation of the vertical profiles to scale the POLCOMS depths to the current FVCOM node's depth range. This means the full profile structure is maintained in the interpolated profiles but that it is squashed or stretched to fit the scaled depths. This also means the surface and seabed value are fully captured.
      7b3cfce0
  13. 26 Feb, 2013 4 commits