2016issue C0159
Reading a systems catalog as one mechanical procedure
Operators can turn a commercial signal catalog into one mechanical procedure by writing rule inputs, a holding period, and an abstention rule first. Vendor feature fields then work as a checklist. They are not proof that the procedure works.
- A mechanical trading system replaces discretionary interpretation of each decision with automated buy and sell signals generated from rules set in advance.
- Write rule inputs, the holding period, and the abstention rule first, then use feature-catalog fields only as a checklist.
- The same procedure may be delivered as software, as a live signal service, or as a published rule set.
- The catalog does not present track records or comparative rankings, and a companion list ordered by click counts is not an editorial rating.
Start from the procedure, not the listing
A mechanical trading system can replace discretionary interpretation of each decision with automated buy and sell signals generated from rules set in advance. The signal is the prescribed action or inaction emitted when the rules are satisfied. The same procedure may be delivered as software, as a live signal service, or as a published rule set a trader is expected to follow.
One system may rest on a single discipline or combine several, including computational methods, geometric analysis, non-market interpretive frameworks, indicator collections, or custom rules.
What a feature catalog can show
A product catalog can be used to inspect which indicators a system uses, which markets it follows, whether extra applications are required, what support is offered, and what its primary features are. That comparison is a feature catalog: a vendor-authored view of indicators, markets, add-on software, support, and stated features. It is not itself a verified track record.
The catalog format described does not present track records or comparative rankings of the listed systems. Listing content is treated as vendor-supplied and subject to change, and the catalog host declines endorsement and liability for those representations.
Companion lists and accompanying advertisements
A companion list of frequently viewed systems is ordered by click counts and is not an editorial rating. Advertisements accompanying the catalog promote software said to let users build and test systems without writing code.
Turn one listing into one procedure
Editorial: convert a catalog listing into a single mechanical procedure before treating its feature fields as complete. Rule inputs are the market data, state variables, and execution constraints the procedure is allowed to read before it emits a signal. The holding period is the intended time a position remains open under the exit logic of the procedure. The abstention rule is the explicit condition under which the procedure issues no trade rather than forcing an entry or exit.
Editorial: after those three items are written, catalog fields can be checked for indicators, markets, extra applications, support, and stated features. A listing that omits an abstention rule still leaves the procedure incomplete, even when every feature field is filled in.
All readings on this track · 22 readings
- 1985Treat a shared mechanical printout as a public script
- 1988Pessimistic margin ranking for mechanical systems
- 1991From a differenced-average sketch to coded rules
- 2003Commodity enthusiasm is not a complete system
- 2005Reader surveys as system evaluation checklists
- 2008Critiquing unchanged mechanical signals in evolving markets
- 2010Read a mechanical trading system catalog as a specification checklist
- 2011Specify mechanical system signals as one testable procedure
- 2012Treat a packaged mechanical system as one inspectable procedure
- 2013Mechanical trading systems as complete signal procedures
- 2013Testable cycle rules as one procedure
- 2014Evaluate mechanical trading systems as one procedure
- 2015Mechanical trading systems as one testable procedure
- 2016Evaluating mechanical trading systems as testable procedures
- 2016Reading a systems catalog as one mechanical procedure
- 2018Mechanical systems as testable signal procedures
- 2019Treat mechanical system listings as specification audits
- 2019Match the automation stack to mechanical system constraints
- 2019Bar size as a mechanical system construction constraint
- 2020Interrogating mechanical system listings as one procedure
- 2020Mechanical systems still need emotion rules
- 2020Comfort, not theory, keeps mechanical rules in use