Using the ExtData component: Difference between revisions

Line 61:

If you enter a refresh template to update at a certain time each day, month, etc ... as described above there are a few considerations. When ExtData trieds to fill the field at the time described by the template it will once again apply the current model time to the file template, and then try to find data on file at that time. It will not do time interpolation.

The most complex case is if you enter '0' for the represh template. In this case the field gets updated every step and ExtData will try to interpolate to that time using the data on file and can interpolate between data points in different files. In order to accomplish this if you select a refresh template of '0' ExtData tries to find two times that bracket the start time the first time ExtData runs. These get updated as time advances in your application. To find ~~that bracket times and~~ data when starting ExtData ~~applies the current time to the file template and~~ looks for two times on the file that bracket the current time. ~~Now~~ what ~~happens if it can't find both times on the file? For example suppose the current time is greater than the last time on the file it looked at when it applied the current~~ time to the file template ~~and examined what was in~~ the ~~file~~. This is where the idea of a file frequency comes in. You as the user can specify a file frequency either with the 3 optional key words to the primary export or by letting ExtData "guess" from the file template.

The most complex case is if you enter '0' for the represh template. In this case the field gets updated every step and ExtData will try to interpolate to that time using the data on file and can interpolate between data points in different files. In order to accomplish this if you select a refresh template of '0' ExtData tries to find two times that bracket the start time the first time ExtData runs. These get updated as time advances in your application. To find the bracketing data when starting ExtData looks for two times on the file that bracket the current time. But how does it know what time to apply to the file template is the data is spread across multiple files. This is where the idea of a file frequency and reference time comes in. You as the user can specify a file frequency either with the 3 optional key words to the primary export or by letting ExtData "guess" from the file template. The frequency tells ExtData to advance the time by the frequency if it can't find what it needs using the current time, apply this new time to the file template, and finally check

=== Masks ===

=== Derived Exports ===

@@ Line 61: / Line 61: @@
 If you enter a refresh template to update at a certain time each day, month, etc ... as described above there are a few considerations. When ExtData trieds to fill the field at the time described by the template it will once again apply the current model time to the file template, and then try to find data on file at that time. It will not do time interpolation.
-The most complex case is if you enter '0' for the represh template. In this case the field gets updated every step and ExtData will try to interpolate to that time using the data on file and can interpolate between data points in different files. In order to accomplish this if you select a refresh template of '0' ExtData tries to find two times that bracket the start time the first time ExtData runs. These get updated as time advances in your application. To find that bracket times and data when starting ExtData applies the current time to the file template and looks for two times on the file that bracket the current time. Now what happens if it can't find both times on the file? For example suppose the current time is greater than the last time on the file it looked at when it applied the current time to the file template and examined what was in the file. This is where the idea of a file frequency comes in. You as the user can specify a file frequency either with the 3 optional key words to the primary export or by letting ExtData "guess" from the file template.
+The most complex case is if you enter '0' for the represh template. In this case the field gets updated every step and ExtData will try to interpolate to that time using the data on file and can interpolate between data points in different files. In order to accomplish this if you select a refresh template of '0' ExtData tries to find two times that bracket the start time the first time ExtData runs. These get updated as time advances in your application. To find the bracketing data when starting ExtData looks for two times on the file that bracket the current time. But how does it know what time to apply to the file template is the data is spread across multiple files. This is where the idea of a file frequency and reference time comes in. You as the user can specify a file frequency either with the 3 optional key words to the primary export or by letting ExtData "guess" from the file template. The frequency tells ExtData to advance the time by the frequency if it can't find what it needs using the current time, apply this new time to the file template, and finally check
 === Masks ===
 === Derived Exports ===