Merge pull request #9 from 9808us/develop Contribution: Added new Data Mine to Zeus#4
Merge pull request #9 from 9808us/develop
Contribution: Added new Data Mine to Zeus#4FuzzysTodd wants to merge 8 commits intomasterfrom
Conversation
Contribution: Coding Session - Portfolio Manager E.30
…ormalized Momentum data mine
Contribution: auto adaptative RSI
Contribution: Added new Data Mine to Zeus
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Pull request overview
This pull request adds a new Trading System configuration file named "Lightning-Strike-PM-Demo.json" to the Trading-Systems directory. The file defines a comprehensive algorithmic trading strategy with portfolio management capabilities, including trigger stages, open/close execution stages, and managed stop-loss/take-profit phases.
Key Changes:
- Addition of a complete trading system configuration with entry/exit logic
- Implementation of multiple limit sell orders with incremental profit targets (0.0% to 0.6%)
- Portfolio management system integration with event confirmations and formula management
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "situations": [ | ||
| { | ||
| "type": "Situation", | ||
| "name": "Inmediate Trigger On", |
There was a problem hiding this comment.
Spelling error: "Inmediate" should be "Immediate"
| "name": "Inmediate Trigger On", | |
| "name": "Immediate Trigger On", |
| "situations": [ | ||
| { | ||
| "type": "Situation", | ||
| "name": "Inmediate Take Position", |
There was a problem hiding this comment.
Spelling error: "Inmediate" should be "Immediate"
| "name": "Inmediate Take Position", | |
| "name": "Immediate Take Position", |
| { | ||
| "type": "Condition", | ||
| "name": "New Condition", | ||
| "code": "chart.at24hs.candlesProbability.begin > chart.at24hs.candlesProbability.begin", |
There was a problem hiding this comment.
Unused/duplicate code field: A "code" field is present at the Condition level but appears to be superseded by the "javascriptCode" child node's "code" field. This creates redundancy and the condition-level code field contains a nonsensical comparison: chart.at24hs.candlesProbability.begin > chart.at24hs.candlesProbability.begin (comparing a value to itself, which is always false).
| "code": "chart.at24hs.candlesProbability.begin > chart.at24hs.candlesProbability.begin", |
| { | ||
| "type": "Condition", | ||
| "name": "New Condition", | ||
| "code": "chart.at24hs.candlesProbability.begin > chart.at24hs.candlesProbability.begin", |
There was a problem hiding this comment.
Unused/duplicate code field: A "code" field is present at the Condition level but appears to be superseded by the "javascriptCode" child node's "code" field. This creates redundancy and the condition-level code field contains a nonsensical comparison: chart.at24hs.candlesProbability.begin > chart.at24hs.candlesProbability.begin (comparing a value to itself, which is always false).
| "code": "chart.at24hs.candlesProbability.begin > chart.at24hs.candlesProbability.begin", |
4 participants
No description provided.