I am trying to run some in-house training sessions for colleagues that are new to using Trendminer.
In our site, our index horizon is set to 1 year, which means that all of the data for the inbuilt training tags (the “TM5” tags, for example TM5-BP2-CONC.1) that are used in the Trendminer training videos is before our time horizon, and is therefore inaccessible for end users.
If we change the general index horizon we would have to reindex every tag, and it would impact our tag resolution/load times. Equally, if I create new bespoke training using our own data, the index horizon will gradually creep forward and new training would have to be updated every year to remain up-to-date with accessible data for people to practice with.
Is there a way to have a different index horizon created for the specific training tags to ensure that the data remains accessible? Is there a way to adjust the date information for the data in the training tags to bring it forward into our time horizon?
Any advice would be greatly appreciated!
Best answer by Wouter Daniels
Hi Jaqqson,
We add a new version of the training tags in every first release of the year (the latest version now is TM6-*), but the data would still sit in the year before, so you would always get in trouble with a 1y index horizon.
Changing the index horizon would not remove the existing index data like changing the resolution would, but I would not recommend changing the index horizon just for the sake of demo data. Setting a different index horizon just for demo tags is currently not possible.
Perhaps a long term solution from our end could be to pre-add next year's version as well (e.g add TM8 tags in the 2027.R1 version), so there is always some data available if your resolution is 1y.
When creating your own demo data, you can create a csv import file of which you regularly update the timestamps. Re-importing the same file will then shift the tag to a more recent time. A more automated solution would be to have the data in a SQL database, and write a SQL query that automatically repeats or shifts the same data.
A tricky thing when shifting tags is that screenshots/recordings that you make will still show timestamps which are now incorrect, which is why we are using new tag names every year rather than simply updating the tags.
For a short-term solution, we would be happy to send you csv files you can import to have a more current version of the tags, or create some accounts for you on our public training server with a longer horizon. Let us know what would work best for you!
We add a new version of the training tags in every first release of the year (the latest version now is TM6-*), but the data would still sit in the year before, so you would always get in trouble with a 1y index horizon.
Changing the index horizon would not remove the existing index data like changing the resolution would, but I would not recommend changing the index horizon just for the sake of demo data. Setting a different index horizon just for demo tags is currently not possible.
Perhaps a long term solution from our end could be to pre-add next year's version as well (e.g add TM8 tags in the 2027.R1 version), so there is always some data available if your resolution is 1y.
When creating your own demo data, you can create a csv import file of which you regularly update the timestamps. Re-importing the same file will then shift the tag to a more recent time. A more automated solution would be to have the data in a SQL database, and write a SQL query that automatically repeats or shifts the same data.
A tricky thing when shifting tags is that screenshots/recordings that you make will still show timestamps which are now incorrect, which is why we are using new tag names every year rather than simply updating the tags.
For a short-term solution, we would be happy to send you csv files you can import to have a more current version of the tags, or create some accounts for you on our public training server with a longer horizon. Let us know what would work best for you!
We add a new version of the training tags in every first release of the year (the latest version now is TM6-*), but the data would still sit in the year before, so you would always get in trouble with a 1y index horizon.
Changing the index horizon would not remove the existing index data like changing the resolution would, but I would not recommend changing the index horizon just for the sake of demo data. Setting a different index horizon just for demo tags is currently not possible.
Perhaps a long term solution from our end could be to pre-add next year's version as well (e.g add TM8 tags in the 2027.R1 version), so there is always some data available if your resolution is 1y.
When creating your own demo data, you can create a csv import file of which you regularly update the timestamps. Re-importing the same file will then shift the tag to a more recent time. A more automated solution would be to have the data in a SQL database, and write a SQL query that automatically repeats or shifts the same data.
A tricky thing when shifting tags is that screenshots/recordings that you make will still show timestamps which are now incorrect, which is why we are using new tag names every year rather than simply updating the tags.
For a short-term solution, we would be happy to send you csv files you can import to have a more current version of the tags, or create some accounts for you on our public training server with a longer horizon. Let us know what would work best for you!
Wouter
Hi Wouter,
Thanks for your answer, that’s very helpful! We’d be very happy to get a copy of the csv files so we can work out our own training data with modified dates. How do I get in touch to request a copy?
