Topic: Consistent naming of EAs
Consistent naming of EAs is most important when amount of strategies and descendants of those strategies will quickly grow. Here is my proposal. It is self-explanatory, but few comments may help.
As you can see it is a modular system. When those files are listed in a directory they will arrange automatically so the “parent” EA and all “descendants” will be grouped together. This will help to manage “parent” strategies and “descendants” of each EA.
Each token is initiated by token number, to differentiate its field from other tokens. Probably it could be done without numbering each token in this way, just by using placing in the string as information. But token numbering will give (maybe?) better sorting in directories and better readability.
Amount of sub-versions can be changed to accommodate your particular needs. I have here three sub-versions but maybe two are enough. Amount of digits in each sub version can be also different from shown. But I have chosen to have the same amount of digits in all subversions to simplify modularity (i.e. simplify readability).
Numbers used in subversions can have coded meanings. For example Sub Version B can have following coding:
4 01 – scalping mostly
4 02 – has problem with exits
4 09 – ready for live trading
File names could have additional information added in form of letters (which could give a simpler system comparing to the coding with numbers), but I wanted to develop a system with same file name and ID/Magic Number.
This system will result in long file names and ID numbers, but keeping things organized is worth the price of this burden?
I am just starting to use this numbering system and the problem I have is to consolidate it with all the EAs produced before, with names following many different conventions.
Your input will be most appreciated!