Announcement

Collapse
No announcement yet.

Partner 728x90

Collapse

MAE and MFE clearly wrong

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #31
    Hello butt_toast,

    Thank you for your reply.

    The number you provided in your last post is a support ticket number and I do not see any reference to a feature request or other tracking number in that ticket.

    That being said, our development team is treating this as a feature request and we do have a current feature request to calculate MAE/MFE values on a per contract basis. I've added a vote to this request on your behalf. This is being tracked under the number SFT-4168.

    As with all feature requests, interest is tracked before implementation is considered, so we cannot offer an ETA or promise of fulfillment. If implemented, it will be noted in the Release Notes page of the Help Guide.

    Release Notes — https://ninjatrader.com/support/help...ease_notes.htm

    Please let us know if we may be of further assistance to you.

    Kate W.NinjaTrader Customer Service

    Comment


      #32
      Originally posted by NinjaTrader_Kate View Post
      Hello butt_toast,

      Thank you for your reply.

      The number you provided in your last post is a support ticket number and I do not see any reference to a feature request or other tracking number in that ticket.

      That being said, our development team is treating this as a feature request and we do have a current feature request to calculate MAE/MFE values on a per contract basis. I've added a vote to this request on your behalf. This is being tracked under the number SFT-4168.

      As with all feature requests, interest is tracked before implementation is considered, so we cannot offer an ETA or promise of fulfillment. If implemented, it will be noted in the Release Notes page of the Help Guide.

      Release Notes — https://ninjatrader.com/support/help...ease_notes.htm

      Please let us know if we may be of further assistance to you.
      The reason this is not a feature request is that the feature exists. The number shown is incorrect. It's a bug. This is very clear. The only way this can be seen as a feature rather than a bug is if you change the definition and use of an industry standard metric to something incorrect and unique to this software.

      It's like if you're driving a car and monitoring your speed in MPH. You are driving 70 MPH and the speedometer is telling you that you're driving 210 MPH because you have driven three miles. You bring this error to the attention of the car manufacturer and they tell you it's a feature of their speedometer because to them MPH is multiplied by the number of miles driven.

      I understand that you have limited recourse, and I appreciate you doing what is within your power, just please do so in good faith.

      Comment

      Latest Posts

      Collapse

      Topics Statistics Last Post
      Started by Segwin, 05-07-2018, 02:15 PM
      10 responses
      1,767 views
      0 likes
      Last Post Leafcutter  
      Started by Rapine Heihei, 04-23-2024, 07:51 PM
      2 responses
      30 views
      0 likes
      Last Post Max238
      by Max238
       
      Started by Shansen, 08-30-2019, 10:18 PM
      24 responses
      943 views
      0 likes
      Last Post spwizard  
      Started by Max238, Today, 01:28 AM
      0 responses
      9 views
      0 likes
      Last Post Max238
      by Max238
       
      Started by rocketman7, Today, 01:00 AM
      0 responses
      7 views
      0 likes
      Last Post rocketman7  
      Working...
      X