OPTION: with a large table (or a small number of tables)

 Core idea

Keep the data together (with low probability of changes in the data structure and risk of interference..) 

 Method I: filter

Here you select the data by reading everything and applying a filter afterwards.
Easy to implement but ciumputationaly expensive

 Method II:Query

Here you select via  Importing data from SQL sources 3.1

 

OPTION: switching between tables

Core idea

If you need several tables, it might be easier to switch between such sets

E.G. Scenario A, B, Cif you need

This is good, if you do NOT want to mix the data.
It also good if you would like to use different sets of parameters.

Editable grids and Charts ae easier this way.

Method I: Parameters Approach

Using parameters for the path's of the tables

Method II: Copy

Copy or delete TIS tables  

OPTION: within TIS-Editor (very old approach)

Background

Very often it is helpful to be able to switch between data sets. E.g.

  • Dataset A is the full data that should be calculated but it takes long to calculate
  • Dataset B is a short dataset, that makes development much faster

There are two areas where so switching is of relevance:

  • For human developers
  • For the Solution Runner, as the solution runner of changes references between nodes but refers to node by names.

Preparing switches for developers

It is helpful to encode information on what could be the input nodes for a specific node in the name of a node:

An Example for such an encoding:

  • E indicates: this is an optional input node for Switch E
  • F indicates: this is an optional input node for Switch E

    E indicates: This is switch E
    F indicates: this is switch F

    Resume: b1_3 0 can reference b1_20, b1_21, b1_22

    There is no enforced coding convention. The above example is the one used in the forecasting package.

    NOTE: Often switches have to take place in parallel. E.g. in the Forecasting package one should switch in parallel between the Forecasting data and a corresponding Calendar. Otherwise the two would not fit.

Switches for the Solution Runner

IMPORTANT: Some names of nodes used by the solution runner should not be changed without corresponding change in the Solution Runner.

Correspondingly, it is helpful to encode information on what could be nodes for the Solution Runner. A possible convention is to encode this information in an Appendix with the letters SR