Issue with simple script | Forex Factory

Options

Permalinks
Print Thread

Similar Threads

Help with converting a script from pine script(TradingView) 0 replies

Basic Alt Key/Entry Script - Simplest Script Ever 1 reply

i like to add an indicator script into my own script. what would be the best idea? 3 replies

Simple Script Of Low/high Previous DAY !? 6 replies

Simple Script 13 replies

Attachments: Issue with simple script
Exit Attachments

Issue with simple script

  • #1
  • First Post: Dec 13, 2024 4:27pm Dec 13, 2024 4:27pm
Hello, I have a simple script thats suppossed to load a template. However, it doesnt work always citing that the template cant be found. I have tried multiple template that I know for a fact exist and yet it wont work. Can anyone rectify the issue?
Attached File(s)
File Type: mq4 Load Template.mq4   2 KB | 170 downloads
  • #2
  • Dec 13, 2024 6:06pm Dec 13, 2024 6:06pm
Quoting wowzers
Hello, I have a simple script thats suppossed to load a template. However, it doesnt work always citing that the template cant be found. I have tried multiple template that I know for a fact exist and yet it wont work. Can anyone rectify the issue? {file}
I have made this about as simple as it gets. Wouldn't it be just as easy to load your template from the MT4 template list?
Attached File(s)
File Type: mq4 Load Template.mq4   < 1 KB | 184 downloads
Trade what you see not what you hope
  • #3
  • Dec 14, 2024 1:08am Dec 14, 2024 1:08am
Quoting cja
{quote} I have made this about as simple as it gets. Wouldn't it be just as easy to load your template from the MT4 template list? {file}
The idea was to be able to hotkey a script to reload a template on strategy tester because the indi I was testing relied on a higher tf for calculation. I was going to just try to reload the template with the script every few bars so that I could see how the indi fared. If I manually reload the template with the list as you said it works but thats tedious and was trying something out. Unfortunately, this script doesnt seem to work on strategy tester.
  • #4
  • Edited 3:48am Dec 15, 2024 3:34am | Edited 3:48am
Quoting wowzers
{quote} The idea was to be able to hotkey a script to reload a template on strategy tester...
You don't need a script to achieve what you want. Instead symlink your desired template to "Tester.tpl" before starting the test. I have symlinks for all templates I commonly use in testing. Before starting a test I just rename one of them to "Tester.tpl". This way I don't need to touch the original templates.

Make yourself familiar with the concept of symlinking files. A perfect tool for managing symlinks on Windows is Hermann Schinagle's Link Shell Extension. Depending on your OS you may have to enable "Developer Mode" to use it. Google that.

Be warned that optimization in newer terminal builds has a disastrous bug compared to older builds. This bug manifests itself only when "Tester.tpl" is changed.
Optimizer performance (execution time):

  1. template "Tester.tpl" without indicators, 100 optimizer permutations
    build 500: 4.8 sec
    build 1420: 4.3 sec (1.1 times faster than build 500)
  2. template "Tester.tpl" with custom indicator and lib-calls, 100 optimizer permutations
    build 500: 7.2 sec
    build 1420: 23.4 sec (3.2 times slower than build 500)

If you modify "Tester.tpl" and later on you want to run an optimization, you MUST make sure before that all indicators are removed from "Tester.tpl".

It takes blood, sweat and enough tears to wash away the blood.
  • #5
  • Dec 16, 2024 3:19pm Dec 16, 2024 3:19pm
Quoting emmzett
{quote} You don't need a script to achieve what you want. Instead symlink your desired template to "Tester.tpl" before starting the test. I have symlinks for all templates I commonly use in testing. Before starting a test I just rename one of them to "Tester.tpl". This way I don't need to touch the original templates. Make yourself familiar with the concept of symlinking files. A perfect tool for managing symlinks on Windows is Hermann Schinagle's Link Shell Extension....
Its not about optimizing. I am trying to run an indi that takes calcs from higher timeframes so it needs to load anew to get the correct reading. Thats why simply loading it as tester.tpl wouldnt work because it would load the template the first time correctly but I need it to constantly reload the template for indi to display prooperly.
  • #6
  • Edited Dec 17, 2024 3:09am Dec 16, 2024 3:27pm | Edited Dec 17, 2024 3:09am
Quoting wowzers
{quote} Its not about optimizing. I am trying to run an indi that takes calcs from higher timeframes so it needs to load anew to get the correct reading. Thats why simply loading it as tester.tpl wouldnt work because it would load the template the first time correctly but I need it to constantly reload the template for indi to display prooperly.
If that's the case the indicator you are using is wrongly coded. If it needs to be reloaded to correctly update values (doesn't matter which timeframe) then the indicator implementation is flawed.

Also you have to consider that reading prices from higher timeframes is not easily possible in tester (if the indicator is loaded by a template). Usually you will experience so called "data snooping bias", e.g. an indicator running on M5 and trying to read H1 values will read the next close prices of H1 ahead of time (peeking into the future). Which means if you - for example - want to read the current H1 value at 15:10 your indicator instead reads the H1 value of 16:00.

Usually such approach will invalidate the used indicator or even the full test. It is possible to circumvent this data snooping bias but not with standard MQL functionality.
It takes blood, sweat and enough tears to wash away the blood.
  • #7
  • Last Post: Dec 17, 2024 11:00pm Dec 17, 2024 11:00pm
Quoting emmzett
{quote} If that's the case the indicator you are using is wrongly coded. If it needs to be reloaded to correctly update values (doesn't matter which timeframe) then the indicator implementation is flawed. Also you have to consider that reading prices from higher timeframes is not easily possible in tester (if the indicator is loaded by a template). Usually you will experience so called "data snooping bias", e.g. an indicator running on M5 and trying to read H1 values will read the next close prices of H1 ahead of time (peeking into the future)....
Yes, I figure its wrongly coded. I have come across many indis that are wrongly coded but envisioned that there has to be some kind of simple solution of reloading the template every bar to give us a somewhat accurate idea of what that particular indi is about. Right now, I load a manual EA on strategy tester (that allows me to trade manually) and then load the indi on a template to see if it has any validity but these wrongly coded indis are an issue I consistently run into and I feel there is a simple reloading template workaround but havent figured it out yet.
0 traders viewing now