Superalgos/docs/_includes/data_mine/process-definition.md

{% assign title = "Process Definition" %} {% assign definition = site.data.data_mine.process_definition %} {% assign preposition = "a" %} {% assign plural = "s" %}

{% if include.more == "yes" and include.heading == "more" %}

Click to learn more about {{ title | downcase }}{{plural}}

{% endif %}

{% if include.heading != "" and include.heading != "more" %} {{include.heading}} {{title}} {% endif %}

{% if include.icon != "no" %}

{% if include.table == "yes" and include.icon != "no" %}

{% endif %} {% if include.table == "yes" and include.icon != "no" %}

{% endif %} {% endif %} {% if include.definition == "bold" %} {{ definition }} {% else %} {% if include.definition != "no" %} {{ definition }} {% endif %} {% endif %} {% if include.table == "yes" and include.icon != "no" %}

{% endif %}

{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}

Click to learn more about {{ title | downcase }}{{plural}}

{% endif %}

{% if include.content != "no" %}

As hinted above, most bots, in particular indicators, have two different processes. The reason is that different data structures need to be handled in different manners. The Multi-Period-Daily process handles daily files, while the Multi-Period-Market process handles market files.

{% endif %}

{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}

Click to learn more about {{ title | downcase }}{{plural}}

{% endif %}

{% if include.adding != "" %}

{{include.adding}} Adding {{preposition}} {{title}} Node

To add a process definition, select Add Process Definition on the bot's menu. A process definition node is created along with the basic structure of nodes comprising the definition.

{% endif %}

{% if include.configuring != "" %}

{{include.configuring}} Configuring the {{title}}

Select Configure Process on the menu to access the configuration.

Multi-Period-Market:

{
  "codeName": "Multi-Period-Market",
  "description": "Brief description of what the bot does.",
  "startMode": {
    "allMonths": {
    "run": "false",
    "minYear": "",
    "maxYear": ""
  },
  "oneMonth": {
    "run": "false",
    "year": "",
    "month": ""
  },
  "noTime": {
      "run": "true"
    },
    "fixedInterval": {
      "run": "false",
      "interval": 0
    }
  },
  "deadWaitTime": 0,
  "normalWaitTime": 0,
  "retryWaitTime": 10000,
  "sleepWaitTime": 3600000,
  "comaWaitTime": 86400000,
  "framework": {
    "name": "Multi-Period-Market",
    "startDate": {
    },
    "endDate": {
    }
  }
}

Multi-Period-Daily:

{
  "codeName": "Multi-Period-Daily",
  "description": "Brief description of what the bot does.",
  "startMode": {
    "allMonths": {
      "run": "false",
      "minYear": "",
      "maxYear": ""
    },
    "oneMonth": {
      "run": "false",
      "year": "",
      "month": ""
    },
    "noTime": {
      "run": "true"
    },
    "fixedInterval": {
      "run": "false",
      "interval": 0
    }
  },
  "deadWaitTime": 0,
  "normalWaitTime": 0,
  "retryWaitTime": 10000,
  "sleepWaitTime": 3600000,
  "comaWaitTime": 86400000,
  "framework": {
    "name": "Multi-Period-Daily",
    "startDate": {
      "takeItFromStatusDependency": 0
    },
    "endDate": {
      "takeItFromStatusDependency": 1
    }
  }
}

Both configurations deal with certain aspects of the internal workings of these kinds of processes. These are the ones to be adjusted when creating a new bot:

• codeName is the name of the process as used within the code of the system; for consistency, always use Multi-Period-Market and Multi-Period-Daily accordingly.

• description is a short description of what the bot does.

{% endif %}

{% if include.starting != "" %}

{{include.starting}} Starting {{preposition}} {{title}}

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

{% endif %}

{% if include.more == "yes" %}

{% endif %}