Timespan is not taken into account in a granule

If you selected the "1w" (one week)  timespan in SEAScope but only get 1 granule for the Geostrophic current after the extraction is complete, it probably means that you did not follow the instructions provided in slide 6 of the presentation you linked.

By default the config.ini file for "GlobCurrent geotrophic current" collection has the mustBeCurrent parameter set to True, so that SEAScope only displays the granule which intersects the current datetime. This is the behavior you seem to witness.

SEAScope can only perform extraction on data displayed on the screen, and for the lagrangian advection notebook we need to extract several GlobCurrent geostrophic current granules at once, so we have to modify the aforementioned configuration to alter SEAScope behavior for this collection and get it to display several days of geostrophic current at once.

The instructions in slide 6 provide a new config.ini where mustBeCurrent has been set to False, so that SEAScope can display (and therefore extract) "GlobCurrent geostrophic current" granules as long as there time coverage intersects SEAScope selected timespan (one week evenly distributed around the current date).

Doing so should allow you to extract the data required in the notebook and to perform the advection. Let us know if there are other issues.

PS: regarding your question about the k_u variable: the extractions object is an unsorted list of extracted data, but we need these data sorted in chronological order so we build the k_u list which contains the indices of extracted data sorted by time (the beginning of their time coverage actually, obtained with ['meta']['start']).

Messages In This Thread
RE: Timespan is not taken into account in a granule - by Sylvain Herlédan - 2019-07-08T07:56 AM

Forum Jump: