Using the ExtData component: Difference between revisions
Line 61: | Line 61: | ||
If you enter '-' the field will be updated only the first time ExtData runs. It will take the current model time and try to interpolate to that time using the available data. | If you enter '-' the field will be updated only the first time ExtData runs. It will take the current model time and try to interpolate to that time using the available data. | ||
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 tries to fill the field at the time described by the template it will once again apply the current model time to the file template, then interpolate to that time using the available data. | 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 tries to fill the field at the time described by the template it will once again apply the current model time to the file template, then interpolate to that time using the available data. | ||
If you enter '0' for the refresh template the field gets updated every step and ExtData will try to interpolate to the application time using the data on file. | If you enter '0' for the refresh template the field gets updated every step and ExtData will try to interpolate to the application time using the data on file. | ||
Let me repeat, ExtData always tries to interpolate to the time you tell it | [[Let me repeat, ExtData always tries to interpolate to the time you tell it to using the data on the file or files you reference. To do this at any time your application will encounter, whether it is the application time or a time that gets produced by evaluating a refresh template ExtData must be able to find two times on the data series that bracket this time. These need not be on the same file as it can interpolate between data on different files. This is key to understanding how ExtData functions]] | ||