Troubleshooting Missing CTA Strategies in VeighNa

Summary

This VeighNa community exchange addresses a strategy that does not appear in the CTA backtesting strategy menu after its files have been copied into the installation. The suggested checks are to place strategy files in a scanned strategies directory, confirm that each strategy class has a unique name, verify that files use the Python extension, and restart the application so it reloads the list. The original poster reports that duplicate class names were the cause in their case.

The exchange is a brief platform troubleshooting example rather than a trading method or analysis. It offers practical points for diagnosing why only some strategy files are discovered, but does not explain VeighNa's loader behavior in depth or cover error logs, imports, or other possible causes. The reported resolution supports checking class-name uniqueness, though the advice should be treated as a starting checklist rather than a complete diagnosis for every installation.

Key ideas

• VeighNa CTA strategies must be stored in a directory the platform scans.
• Strategy class names need to be unique across loaded strategies.
• Files should have the Python file extension, and restarting may refresh the strategy list.
• The user resolved their issue after finding that strategy class names were duplicated.
• The forum post offers a limited troubleshooting checklist, not a complete account of loader failures.

Tags

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