# Changes between Version 41 and Version 42 of EcomsUdg/RPackage/Functions

Ignore:
Timestamp:
Aug 29, 2013 9:36:56 AM (9 years ago)
Comment:

--

### Legend:

Unmodified
 v41 * Data: 2D matrix with the time series for each of the stations arranged by columns. === ''__Note__'' An option to read station data from NetCDF files is currently under development and it is expected to be available by the next release of meteoR. === ''__Examples__'' === ''__Details__'' Regarding the spatial component of the returned data, the function can select the whole spatial domain covered by the dataset (in this case lonLim = NULL and latLim = NULL), spatial windows defined by the minimum and maximum corner coordinates (for instance lonLim = c(-10,10) and latLim = c(35,45) indicates a rectangular window), and single grid-cell values (for instance lonLim = -3.21 and latLim = 41.087 for retrieving the data in the closest grid point to the point coordinate -3.21E , 41.087N). In the last two cases, the function operates by finding the closest (euclidean distance) grid-points to the coordinates introduced. The function has been implemented to access seasonal slices (as determined by the season argument. Seasons can be defined in several ways: A single month (e.g. season = 1 for January), a standard season (e.g. season=c(1,2,3) for JFM, or season=c(12,1,2) for DJF), or any period of consecutive months (e.g. season=c(1,2,3,4,5,6), for the first half of the year). Seasons are returned for a given year period (defined by the years argument, e.g. years = 1981:2000) with a homogeneous forecast lead time (as given by the leadMonth argument; e.g. leadMonth = 1 for one-month lead time) with respect to the first month of the selected season. For example, season=c(1,2,3) for years = 1995:2000 and leadMonth = 1 will return the following series: JFM 1995 (from the December 1994 runtime forecast), ..., JFM 2000 (from the December 1999 runtime forecast). Note that it is also possible to work with year-crossing seasons, such as DJF. In this case,  season=c(12,1,2) for years = 1995:2000 and  leadMonth = 1 will return the following series: DJF 1994/1995 (from the November 1994 runtime forecast), ..., DJF 1999/2000 (from the November 1999 runtime forecast). Regarding the spatial component of the returned data, the function can select the whole spatial domain covered by the dataset (in this case lonLim = NULL and latLim = NULL), spatial windows defined by the minimum and maximum corner coordinates (for instance lonLim = c(-10,10) and latLim = c(35,45) indicates a rectangular window), and single grid-cell values (for instance lonLim = -3.21 and latLim = 41.087 for retrieving the data in the closest grid point to the point coordinate -3.21E , 41.087N). In the last two cases, the function operates by finding the nearest (euclidean distance) grid-points to the coordinates introduced. The function has been implemented to access seasonal slices (as determined by the season argument. Seasons can be defined in several ways: A single month (e.g. season = 1 for January), a standard season (e.g. season=c(1,2,3) for JFM, or season=c(12,1,2) for DJF), or any period of consecutive months (e.g. season=c(1:6), for the first half of the year). Seasons are returned for a given year period (defined by the years argument, e.g. years = 1981:2000) with a homogeneous forecast lead time (as given by the leadMonth argument; e.g. leadMonth = 1 for one-month lead time) with respect to the first month of the selected season. For example, season=c(1,2,3) for years = 1995:2000 and leadMonth = 1 will return the following series: JFM 1995 from the December 1994 runtime forecast, ..., JFM 2000 from the December 1999 runtime forecast. Note that it is also possible to work with year-crossing seasons, such as DJF. In this case,  season=c(12,1,2) for years = 1995:2000 and  leadMonth = 1 will return the following series: DJF 1994/1995 (from the November 1994 runtime forecast), ..., DJF 1999/2000 (from the November 1999 runtime forecast).