Ehler’s MESA indicators constantly reload/recalculate?

• 06/26/2018 at 12:15 AM #74351
  kamy

  Hi Bard

  I have searched and failed to find the itf files for the MESA indicators you reference here. Could you point me to where they are available from?

  Many Thanks

  Kamy

  

  kamy

  Participant

  Topics: 0

  Replies: 1

  Been thanked: 0 times
  06/26/2018 at 3:39 PM #74447
  Bard

  Hi Ingrid,

  I was surprised and disappointed to learn from IG Index that I am expected to now wait until the next PRT platform upgrade for a fix to a problem that was caused by a PRT platform upgrade, and that there is no given date for that platform update? No date?

  After having invested so much of my valuable time with this PRT platform (learning how the coding works, testing automated strategies after having used the highly reliable Trading Blox s/ware) and having to pay for the service that hasn’t been functioning with these MESA indicators for over a year, I’m now left wondering what the best solution is and if I will have to find another platform, eg like eSignal or something. This is a pity as PRT has so many features to commend it.

  Re the need to use Ehler’s MESA indicators, over the classic indicators used in most charting packages including PRT, I regard the vast majority of them as dated, generally non logarithmic and unlikely to produce any statistical edge long term from an automated point of view.

  Best Regards
  Bard

  

  Bard

  Participant

  Topics: 138

  Replies: 814

  Been thanked: 99 times
  07/06/2018 at 3:40 PM #75487
  Ingrid

  Dear Bard,

  There seems to be a misunderstanding between our engineer team and the IG support team.
  Our engineer team would actually need from you to resend a technical report with a code access to your indicators as follows:

  – As soon as you encounter the issue, go to the “Help” menu on the ProRealTime toolbar.
  – Please assure that the window concerned by this issue is open.
  – Click on “Help center”, then on “I have a technical problem”
  – Choose the category “Automatic trading”
  – Give the name of the code you are referring to.
  – To benefit from a technical help we need you to authorize us the access to the crypted code. To give us a temporary access, please check the box “I authorize the decryption of the codes (…)”
  – Give as many details as possible, explain the issue you are having in the text box and mention
  – Click “Send report”

  This will send us a report containing technical information concerning your platform, which will allow our technical team to run a diagnostic analysis of the issue you have come across.

  In the meanwhile, we suggest you to reduce the amount of units displayed on your chart.

  Many thanks in advance for your patience and cooperation,

  

  Ingrid

  Moderator

  ProRealTime

  Topics: 1

  Replies: 9

  Been thanked: 3 times
  07/10/2018 at 12:05 PM #75710
  Bard

  Thanks Ingrid,

  I sent the report. They replied that the indicator is recalculating itself because of Call Functions within it. That’s  interesting, mainly because the code has never been changed: It always had Call Functions within the different individual indicators that make up the whole MESA indicator system and it worked on the previous version of PRT.

  Am I correct, that the solution now is to either (1) wait for the PRT platform upgrade as mentioned in a previous IG Index email I received or to (2) remove the “Call Functions.” Also is there any way of knowing if the next PRT upgrade will in fact solve the issue?

  Best regards
  Bard

   

   

  

  Bard

  Participant

  Topics: 138

  Replies: 814

  Been thanked: 99 times
  11/01/2018 at 11:41 AM #83917
  Jakub

  Hi Bard,

  I have retreived the technical analysis of your case and I beleive that you received the analysis privately.

  Indicators are calculated in
  real time, so if there is a tick every second then the code might calculated
  every second.

  In your case, you are using 6 indicators. Almost all of them have call function
  inside them and call for the mesa period indicator. So the platform needs to
  calculate the results for Mesa Period before being able to calculate the
  results for the indicator calling for this.

  There is one indicator in your code which  calls for 4 indicators which, in their turn, call for another
  indicator.

  What happens here is that there are so many calculations that need to be done
  that it causes a delay, and by the time the last indicator has been calculated
  several other ticks were received and the indicators need to be recalculated.
  Since they are all linked, all indicators need to be recalculated and this
  causes further delay.

  The only real solution to avoid this problem is to write the complete code
  instead of using the call function.

   

  Best regards,

  Jakub

  1 user thanked author for this post.

  Bard

  

  Jakub

  Participant

  ProRealTime

  Topics: 0

  Replies: 70

  Been thanked: 24 times
• Author
  Posts