Skip to content
All library documents

Reloading VeighNa Strategies After Code Changes

Article vn.py community
Read the original

Summary

This brief forum exchange explains how VeighNa handles strategy updates after the application has started. For backtesting, users can use the strategy reload control to rescan strategies. For a live trading instance, the reply says that changing instance parameters is possible, but modifications to the strategy’s Python source require restarting the application for the updated code to take effect.

The exchange presents this behavior as intentional, on the premise that strategies used in live trading should already have been tested and stabilized. It is operational guidance about the platform rather than a trading method or evidence about strategy performance. It does not describe a hot-reload mechanism, detail version-specific behavior, or explain how to manage state and positions during a restart, so those practical details remain outside its scope.

Key ideas

  • VeighNa can rescan strategies through a reload control for backtesting.
  • Changing parameters on a live strategy instance is distinct from changing its source code.
  • The forum response says source-code changes require restarting VeighNa to take effect.
  • The rationale given is that live strategies should have been tested and stabilized before deployment.
  • The exchange does not discuss restart procedures, state preservation, or platform-version differences.

Tags

ExecutionBacktesting

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.