Search | User Listing Vidsite | Calendars | Quotes
Home Page ->  Custom TradeTight Routines -> Tools In Team Development -> View ThreadLogon (or Register, or Join TradeTight)

You are logged in as a limited-access Guest.To join TradeTight, first read the info in the Organization & Content room, then click the link above. 

Luke 12:33 (NKJV) ... Sell what you have and give alms; provide yourselves money bags which do not grow old, a treasure in the heavens that does not fail, where no thief approaches nor moth destroys.


Sticky Stradicator Generic TradePlans
Frozen
Jump to page : 1
Now viewing page 1 [50 msgs/pg]
Jump to room :
JimDean
Posted 11/3/2019 1:23 PM (#9763)
Subject: Stradicator Generic TradePlans



Owner/Admin

Posts: 3925
2000100050010010010010025
Location:
USA: GA, Lawrenceville
This thread is dedicated to documentation about the very special TradePlans which provide a way to *fully automate* the mechanical-trading of a Stradicator. They are designed in a "generic" way to work with ANY Stradicator (SCP, CVW, HAT, MMD, etc) ... and interchangeably even with different Versions of a given Strad ... which btw now have very appropos' names of: Base, Flex, Powr, and Wzrd (ie a Strad name might be "SCPpowr", or "CVWflex", or "HATwzrd", or MMDbase").

These are by no means "normal" TradePlans. They rely on special tech that only works with Strad's ... although after the Project is complete, I plan to create a "non-strad" family of them that provides dynamic-scaling features to strategies that aren't based on Stradicators. Each Step of these TP's has multiple Conditions (as few as two, as many as twenty). Each Condition uses a an innovative Routine that links to whatever Stradicator kicked off the trade, and helps manage the flow of the TradePlan in ways that the native TP engine is *incapable* of doing on its own.

The automated trade-management revolves around a "TP Log File" ... not to be confused with the Strad-gen'd TrdLog file (discussed elsewhere) ... the TP Log File keeps track of what happens on every bar of the trade, and is used by the Condition routines to direct *when* and how the TP execution unfolds. At the end of the trade, the TP log file has *complete* info about all order-actions that were taken, as well as the reasons behind them (there are many different "signal basis" possibilities from a Stradicator) ... and, as icing on the cake ... full info about every bar of the trade (even the ones with no Orders).

In this thread, I'll be posting general as well as in-depth explanations about the sixteen alternative generic Stradicator TradePlans ... how they are structured, how they work, and which one(s) you might want to utilize. This is a crucial component of Stradicator functionality, if you want to do automated trading.
Top of the page Bottom of the page
JimDean
Posted 11/3/2019 1:32 PM (#9764 - in reply to #9763)
Subject: Stradicator Generic TradePlans



Owner/Admin

Posts: 3925
2000100050010010010010025
Location:
USA: GA, Lawrenceville
There are 16 variants of the generic-Stradicator TradePlans which handle increasing degrees of trade-management sophistication: TPXntry, TPXpxit, TPXadds, TPXsmrt ... each of which has a variant for 4 Order types (moC, moO, Boo, mKt). Each TradePlan uses special Plan Conditions that provide a bridge between the Stradicator actions in the present, the Log File that tracks the past, and the TradePlan engine that directs the Broker. The 16 variants have a common naming-structure: TPXyyyy & PCXyyyy, where "X"=C|O|B|K (moC, moO, Boo, mKt), and "yyyy" = ntry|pxit|adds|smrt.

Of the four generic Stradicator TradePlans, the Ntry TP is simplest ... but even so, it supports very useful scaled-entry options (Toe+Confirm, or Regular ... in a variety of 20%-size-steps), and all types of Stradicator Full-Exits. The PXit TP does all that, plus fully supporting Stradicator Partial Exits (which can occur anywhere in the trade, to Grab Profits or to Cut Losses, for a variety of reasons ... extremely powerful. Next in line, the Adds TP allows the Stradicator's logic to increase the position-size after a Partial Exit pullback, under very strict rules ... a great way to (cautiously) "let your profits run". The Smrt TP pulls out all the stops ... doing everything the others do, but in a more refined way (10% size-change increments rather than just 20% options) ... incorporating Smart-Sizing rules for position-size changes and/or the gap-widths for the six "envelope-exits" (3 Grab, 3 Cut). To do this, the Smrt TP is approximately 50x longer than the Ntry TP ... but since it's generic, no one ever has to touch it ... all these TP's are self-contained with no need for users to modify them, and they work with *every* Stradicator.
Top of the page Bottom of the page
JimDean
Posted 11/3/2019 1:41 PM (#9765 - in reply to #9764)
Subject: Stradicator Generic TradePlans



Owner/Admin

Posts: 3925
2000100050010010010010025
Location:
USA: GA, Lawrenceville
... much more info to come ...

I've created a spreadsheet that is (mostly) automatic, which generates tabular output defining every aspect of the TradePlan structure. From that, Ken Wilsdon (bless his heart), will do a LOT of careful typing in the TradePlan Editor, to manually enter every condition and order for every step of of every TP ... a huge task that once complete, will never need anyone else to fiddle with it (he's being exclusively given a copy of the autogen-spreadsheet, as thanks for his efforts).

I've already defined the scope and details about how the Condition routines and Log Files will operate ... I'm working on that now, so that the very first Strad released will have been tested using the TP's. This is a significantly better schedule than I'd expected ... thanks to Ken's willingness to help out ... the TP's weren't planned for release until the last Strad was delivered.
Top of the page Bottom of the page
Jump to page : 1
Now viewing page 1 [50 msgs/pg]
( E-mail a Link | Printer Version | Search Room )
Frozen

Owner of site: Jim Dean -- Forum content is confidential, and may not be distributed without written permission.