MACD scan results are inaccurate

• 02/15/2021 at 11:38 PM #161561
  Larrikin

  As the title suggests, I’m getting inaccurate results when scanning for a MACD Line crossing (above or below) the MACD Signal line.

  I created a scan without any other variables (see image) and it still returned inaccurate results.

  This is an important scan for me so I would really appreciate the help to have it corrected, please?

   

  Thank you,

  David

  

  Larrikin

  Participant

  Topics: 5

  Replies: 2

  Been thanked: 1 time
  02/16/2021 at 10:38 AM #161615
  Nicolas

  Something is wrong you are right. Could you please send a ticket report, reffering to this topic please? I’ll do the same.

  In the meantime, you can use this accurate version which is using codes to calculate the MACD:

  linecode = average[12,1]-average[26,1] signalcode = average[9,1](linecode) testcode = linecode crosses over signalcode screener[testcode]

  1 2 3 4 5

  linecode = average[12,1]-average[26,1] signalcode = average[9,1](linecode) testcode = linecode crosses over signalcode   screener[testcode]

  for the record, the version that is not working is:

  iline = MACDline[12,26,9](close) signal = MACDSignal[12,26,9](close) test = iline crosses over signal screener[test]

  1 2 3 4 5

  iline = MACDline[12,26,9](close) signal = MACDSignal[12,26,9](close) test = iline crosses over signal   screener[test]

   

  1 user thanked author for this post.

  Larrikin

  

  Nicolas

  Keymaster

  Topics: 81

  Replies: 20863

  Been thanked: 4775 times
  04/07/2021 at 2:06 AM #166362
  Larrikin

  Here is an email reply from tech support regarding the problem.

  David.

  “Following your request, please note first of all that the code which is generated by the simplified programming of the ProScreener is correct (MACD Line crosses over the MACD Signal).
  However, there is a problem with the calculation of the MACD Signal in the ProScreener, but it is due to an internal calculation problem of the engine.
  We have identified the problem and our technical team is currently working on a correction, which will be implemented as soon as possible.
  Please note that depending on the complexity of the correction needed, it may take up to several weeks for the problem to be corrected.”

  1 user thanked author for this post.

  Nicolas

  

  Larrikin

  Participant

  Topics: 5

  Replies: 2

  Been thanked: 1 time
• Author
  Posts