Changes between Version 92 and Version 93 of udg/ecoms/dataserver/catalog

Timestamp:

May 11, 2016 1:54:10 PM (6 years ago)

Author:

gutierjm

Comment:

--

udg/ecoms/dataserver/catalog

@@ -80 +80 @@
 == GloSea5 (provided by Met-Office) 
 
-GloSea5 data have been exposed as two different virtual datasets through ECOMS-UDG, based on their different forecast extents, initializations and member configuration. Members are defined from all combinations of the members and lagged runtimes.
-
-In particular, in UDG members are ordered considering all combinations of member `x` runtime, being member the factor that varies fastest. For instance, a call to `loadECOMS` using `members = 1:5` in `dataset = Glosea5_seasonal_12` will return, in this order, the following 5 members:
-
-Member1: [member1,runtime1]
-
-Member2: [member2,runtime1]
-
-Member3: [member3,runtime1]
-
-Member4: [member4,runtime1]
-
-Member5: [member1,runtime2]
-
-
-The main characteristics of both GloSea5 hindcasts are are next enumerated:
-
+GloSea5 data have been exposed as two different virtual datasets through ECOMS-UDG, based on their different forecast extents, initializations and member configuration:
 [=#gs5_12]
 * '''[http://meteo.unican.es/tds5/catalogs/glosea5/glosea5Datasets.html?dataset=glosea5/day_GloSea5_12_members_seasonal_sfc.ncml Glosea5_seasonal_12]''' 
@@ -112 +96 @@
   - Hindcast period: 1992-2013
 
+Members are defined from all combinations of the members and lagged runtimes. In particular, in UDG members are ordered considering all combinations of member `x` runtime, being member the factor that varies fastest. For instance, a call to `loadECOMS` using `members = 1:5` in `dataset = Glosea5_seasonal_12` will return, in this order, the following 5 members: Member1: [member1,runtime1],
+Member2: [member2,runtime1],
+Member3: [member3,runtime1],
+Member4: [member4,runtime1],
+Member5: [member1,runtime2].
+
+