Using the ExtData component: Difference between revisions

Line 100:

=== Special Options ===

There are several special options and cases that the user should be aware of.

==== Time Offset in Continuous Update ====

If the user specifies a refresh template of 0, they can tell ExtData to apply a time offset when updating the variable. If they enter 0;0300 when updating the variable it will use an offset of +30 minutes when time interpolating to update the variable.

==== Climatologies ====

Sometimes data represents a yearly climatology. ExtData currently only supports 12 month climatologies, i.e. one time per month. If the climatology keyword is set to yes you are telling ExtData that you have a file with 12 times spanning at year or 12 files, one per month. In either case ExtData does not use the application clock's year but replaces it with the year in the file for interpolation and wraps the data around at the end of the year.

==== Constant Files ====

Occasionally the user might want to satisfy a variable with a data set that is constant (not in the sense that you want to set the import to the same value but you have some geospatial data with only one time on a file that has no tokens) and should not be time interpolated. If the user specifies "-" for the refresh template (update once) and ExtData finds that the file template has not tokens, and that the file itself only has one time, ExtData will note this and update the variable once, and update the variable once with this set of data.

==== Vector Variables ====

When importing winds into an application the user has the option to handle these specially so that the u and v components are not separately treated as scalars, but as proper vector quantities when regridding to the target grid. Currently this is only supported when going from Lat-Lon data to an application on the Cube-Sphere grid. The syntax is for this is as follows:

@@ Line 100: / Line 100: @@
 === Special Options ===
 There are several special options and cases that the user should be aware of.
+==== Time Offset in Continuous Update ====
+If the user specifies a refresh template of 0, they can tell ExtData to apply a time offset when updating the variable. If they enter 0;0300 when updating the variable it will use an offset of +30 minutes when time interpolating to update the variable.
+==== Climatologies ====
+Sometimes data represents a yearly climatology. ExtData currently only supports 12 month climatologies, i.e. one time per month. If the climatology keyword is set to yes you are telling ExtData that you have a file with 12 times spanning at year or 12 files, one per month. In either case ExtData does not use the application clock's year but replaces it with the year in the file for interpolation and wraps the data around at the end of the year.
 ==== Constant Files ====
 Occasionally the user might want to satisfy a variable with a data set that is constant (not in the sense that you want to set the import to the same value but you have some geospatial data with only one time on a file that has no tokens) and should not be time interpolated. If the user specifies "-" for the refresh template (update once) and ExtData finds that the file template has not tokens, and that the file itself only has one time, ExtData will note this and update the variable once, and update the variable once with this set of data.
 ==== Vector Variables ====
 When importing winds into an application the user has the option to handle these specially so that the u and v components are not separately treated as scalars, but as proper vector quantities when regridding to the target grid. Currently this is only supported when going from Lat-Lon data to an application on the Cube-Sphere grid. The syntax is for this is as follows: