Changes between Version 55 and Version 56 of udg/ecoms/RPackage/examples


Ignore:
Timestamp:
Jun 17, 2014 3:21:00 PM (7 years ago)
Author:
juaco
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • udg/ecoms/RPackage/examples

    v55 v56  
    1010The `ecomsUDG.Raccess` package has been built using a (Linux) 32-bit OS, as well as all examples and time estimates. Thus, the performance may vary significantly depending on the aforementioned factors. As a rule of thumb, this would be a recommended usage of the `loadECOMS` function:
    1111
    12 * '''Point-scale''' data retrieval: Objects in this case are relatively small because the longitude and latitude dimensions are dropped. As a result, it is possible to load all members (in the case of forecast datasets) for the whole time span (typically around 30 years) without memory problems.
    13 * '''Regional-Continental''' queries: Depending on the size of the spatial window, it may be possible to access all members, but preferably a few members should be selected, and time spans no longer that a decade.
    14 * '''Global''' queries: It is recommended that in this case single-member, single-year selections are done. 
     12* [wiki:./pointSelection EXAMPLE 1: Single Point Selections]: Objects in this case are relatively small because the longitude and latitude dimensions are dropped. As a result, it is possible to load all members (in the case of forecast datasets) for the whole time span (typically around 30 years) without memory problems.
     13* [wiki:./continentalSelection EXAMPLE 2: Regional-Continental Domain Selections]: Depending on the size of the spatial window, it may be possible to access all members, but preferably a few members should be selected, and time spans no longer than one decade.
     14* [wiki:./globalSelection EXAMPLE 3: Global Domain Selections]: It is recommended that in this case single-member, single-year selections are done. 
    1515
    1616Note that this is just an approximate recommendation. Object sizes also depend on the spatial resolution (CFS has approximately 1º horizontal res., while System4 is 0.75º and WFDEI 0.5º). Similarly, while GCM data will normally return data for the whole Earth (including oceans) for most variables, many observational datasets (like WFDEI) provide only data for land areas.
    1717
    18 = Examples
     18{{{#!comment
    1919
    20 The following examples illustrate the data loading process and can serve as a reference to give estimates of time and resulting object size of typical requests:
     20= Additional examples
    2121
    22 * [wiki:./pointSelection EXAMPLE 1: Single Point Selections]
    23 * [wiki:./continentalSelection EXAMPLE 2: Continental Domain Selections]
    24 * [wiki:./globalSelection EXAMPLE 3: Global Domain Selections]
     22
     23
     24