Would a node-based workflow for automated trading be useful?
PLUTO:
Hello everyone,
I’m currently exploring an idea for automated / quant trading.
The concept is a node-based workflow where users define:
market data → indicators/features → signal → risk rule → execution → monitoring
The framework would then handle the operational parts around it:
I’m mainly curious:
Hello everyone,
I’m currently exploring an idea for automated / quant trading.
The concept is a node-based workflow where users define:
market data → indicators/features → signal → risk rule → execution → monitoring
The framework would then handle the operational parts around it:
- data preparation
- backtesting
- dry-runs / paper trading
- execution logs
- risk checks
- live monitoring
I’m mainly curious:
- Is the bigger pain building the strategy logic, or operating/testing it properly?
- Would a node-based workflow be useful, or would you prefer pure Python/code?
- Which part would you want automated first: data prep, backtesting, dry-run, monitoring, or execution logs?
"Node-Based" workflow. Never heard of that before, but what you are describing is pretty standard no matter if its MQL5, Python or any other language.
A heads-up: Since you are using some sort of an AI, it would be much preferrable to use AI as your tool rather than asking it to come up with stuff such as "node-based". You have reference implementations, open source programs all available to guide you what you want to achieve. Using that to understand what you want is far more beneficial than coming up with "novel" approaches since this well trodden ground
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
I’m currently exploring an idea for automated / quant trading.
The concept is a node-based workflow where users define:
market data → indicators/features → signal → risk rule → execution → monitoring
The framework would then handle the operational parts around it:
- data preparation
- backtesting
- dry-runs / paper trading
- execution logs
- risk checks
- live monitoring
I’m not asking anyone to share their strategy or alpha.I’m mainly curious:
- Is the bigger pain building the strategy logic, or operating/testing it properly?
- Would a node-based workflow be useful, or would you prefer pure Python/code?
- Which part would you want automated first: data prep, backtesting, dry-run, monitoring, or execution logs?
Any feedback would be appreciated. Thank you for reading this!