I understand now that inventors quantify the one-to-one relationship between robots and strategy.
Each created robot can modify the configuration parameters, but it seems that only the corresponding policy can be modified.
In other words, every time a new strategy is created, a new corresponding robot must be built for that strategy in order to test it on the simulation disk.
If so, is it possible to support modifying the corresponding strategies of the robots to facilitate testing and debugging?
bzponyA host can correspond to multiple robots, and a robot can correspond to multiple hosts, right?
The Little DreamThe name is a play on words. I'm not going to lie. BotVS website controls, monitors bots, hosts, and a range of quantitative trading platform features (such as strategy writing feedback, etc.) can be deployed under a BotVS account. Multiple hosts can be deployed under a BotVS account and run on a variety of operating systems, from personal computers to cloud servers (such as Ali Cloud VPS). The software used to manage a bot is a software carrier for a bot that is responsible for scheduling and executing the system's underlying work. It supports a variety of mainstream operating systems. Multiple host programs can be deployed on a device (provided that the performance is set and configured), deploying a host using the unique address of each BotVS account (e.g.: rpcs@a.botvs.com:9902/0766670) as identification, entering the BotVS account password verification, deployment success will display Login OK... etc. The strategy includes specific trading logic, trading methods, event handling, image status display, interaction processing, etc. It also supports JavaScript, Python, C++ writing strategies, binding strategies to run on bots, and using this strategy to implement trading logic to operate trading accounts. When creating a bot, it is necessary to configure certain parameters, bind a policy, configure some exchange objects that need to be operated (representing a specific exchange account), specify on which host the bot runs (servers run by the host), or not specify automatically allocated by BotVS to existing low-load hosts (servers run by the host). Exchange objects are also used to represent objects in an exchange account, adding exchanges, which is the configuration of an exchange account, API KEY (authorization key) or exchange account, only the added exchanges can be selected at the time of creation of the bot, as the exchange objects are configured to the bot. The user information is all configured in the user browser encrypted in the BotVS account, i.e. the BotVS account does not store user plaintext information.
The Little DreamThis is a temporary no-switch policy feature, but it's easy to create a robot. You can also write a policy together, pass a parameter, and switch it in the code to make a policy code work.
hokshelatoSo the current situation is that a robot can only bind one policy A and cannot switch to another policy B after the binding. My question is whether it is possible to support modifying the binding policy so that each robot is free to switch to the policy it wants to use.