Jump to content

JDizzle22

⭐ V.I.P.
  • Posts

    92
  • Joined

  • Last visited

  • Days Won

    2

Reputation Activity

  1. Like
    ⭐ JDizzle22 reacted to Traderbeauty in [REQ] Best Divergence Indicator Very Usefull with Performance Statistics!!   
    Marcelo
    Why is this indicator different than hundreds of others similar ?
    Before you ask for help ( you just joined ) you need to do some research and explain a little deeper than "interesting "
    I would love to see some results on a one directional move up or down and see how does it behave-
    remember- during a strong move up or down you get many fake signals of divergence which are all losers and that is the REAL test of a system and not a sideways day as you posted.
    But no matter what-Thank You for posting- would love to see some other results.
    take care and welcome.
    Traderbeauty-Jane
  2. Like
    ⭐ JDizzle22 got a reaction from ⭐ elishar in How to get rid of unnecessary bar types without creating compiling errors ? Help   
    Bars are removed two ways
    1) bin\Custom\Type OR
    2) DLL--there are two ways to remove
    2a) If you imported the zip file with DLL's, use the remove ninjascript (easiest, but theres another way not discussed here)
    2b) If you copied and pasted the DLL files into bin\Custom, you can delete those files from the folder as long as you did not manually add a reference to them (add reference when you are editing a Ninjascript)
     
    For some DLL's, depending on the vendor, you may have to go through certain steps to remove their software (for example, uninstall from program files and then cleanup the ninja folder). I would make sure you uninstalled all the vendor installation stuff from your machine. Restart, restart ninja, remove more DLL's from remove ninjascript, and remember to compile and then restart ninja for the bar types to be refreshed.
     
    Without knowing what files you have in Custom and Type, there is not really anymore advice I could give.
  3. Like
    ⭐ JDizzle22 got a reaction from ⭐ ESVepara in How to get rid of unnecessary bar types without creating compiling errors ? Help   
    Bars are removed two ways
    1) bin\Custom\Type OR
    2) DLL--there are two ways to remove
    2a) If you imported the zip file with DLL's, use the remove ninjascript (easiest, but theres another way not discussed here)
    2b) If you copied and pasted the DLL files into bin\Custom, you can delete those files from the folder as long as you did not manually add a reference to them (add reference when you are editing a Ninjascript)
     
    For some DLL's, depending on the vendor, you may have to go through certain steps to remove their software (for example, uninstall from program files and then cleanup the ninja folder). I would make sure you uninstalled all the vendor installation stuff from your machine. Restart, restart ninja, remove more DLL's from remove ninjascript, and remember to compile and then restart ninja for the bar types to be refreshed.
     
    Without knowing what files you have in Custom and Type, there is not really anymore advice I could give.
  4. Like
    ⭐ JDizzle22 got a reaction from rhv in How to get rid of unnecessary bar types without creating compiling errors ? Help   
    Bars are removed two ways
    1) bin\Custom\Type OR
    2) DLL--there are two ways to remove
    2a) If you imported the zip file with DLL's, use the remove ninjascript (easiest, but theres another way not discussed here)
    2b) If you copied and pasted the DLL files into bin\Custom, you can delete those files from the folder as long as you did not manually add a reference to them (add reference when you are editing a Ninjascript)
     
    For some DLL's, depending on the vendor, you may have to go through certain steps to remove their software (for example, uninstall from program files and then cleanup the ninja folder). I would make sure you uninstalled all the vendor installation stuff from your machine. Restart, restart ninja, remove more DLL's from remove ninjascript, and remember to compile and then restart ninja for the bar types to be refreshed.
     
    Without knowing what files you have in Custom and Type, there is not really anymore advice I could give.
  5. Like
    ⭐ JDizzle22 got a reaction from Traderbeauty in How to get rid of unnecessary bar types without creating compiling errors ? Help   
    Bars are removed two ways
    1) bin\Custom\Type OR
    2) DLL--there are two ways to remove
    2a) If you imported the zip file with DLL's, use the remove ninjascript (easiest, but theres another way not discussed here)
    2b) If you copied and pasted the DLL files into bin\Custom, you can delete those files from the folder as long as you did not manually add a reference to them (add reference when you are editing a Ninjascript)
     
    For some DLL's, depending on the vendor, you may have to go through certain steps to remove their software (for example, uninstall from program files and then cleanup the ninja folder). I would make sure you uninstalled all the vendor installation stuff from your machine. Restart, restart ninja, remove more DLL's from remove ninjascript, and remember to compile and then restart ninja for the bar types to be refreshed.
     
    Without knowing what files you have in Custom and Type, there is not really anymore advice I could give.
  6. Like
    ⭐ JDizzle22 got a reaction from sheetal in need help to configure Footprint indicators   
    That looks correct on the 2 min. You will have to play with the zoom to get it to how you like (especially on a large time frame you can only get a couple bars on the chart). You can also change the font I think in the settings to make the numbers a bit smaller. In that template just realize that I set it to use NinjaTickFile. So if you switch to binary, make sure you set write data to true. When you do all that you will probably have nothing show up until the market opens next week (unless you download some data from someone else, or run replay data to collect some).
  7. Like
    ⭐ JDizzle22 got a reaction from sheetal in need help to configure Footprint indicators   
    See if this template helps you at all: https://www.sendspace.com/file/x0z3qu
  8. Like
    ⭐ JDizzle22 reacted to ⭐ fxwin in J B @nalytics Trading Thread   
    I agree with Wanderer. Once you are profitable with a system you should buy it, just to be fair with the developer and with yourself.
  9. Like
    ⭐ JDizzle22 got a reaction from sheetal in need help to configure Footprint indicators   
    Are both of those charts yours, or is the first one someone else's?
     
    You have it set to "Binary" which means if you don't have the data already recorded it wont' show up. You can download the data here: https://www.bigmiketrading.com/elite-circle/7279-official-gomrecorder-qcollector-tick-data-sharing-thread.html
     
    You can also use updown tick, set Binary to NinjaTickFile
  10. Like
    ⭐ JDizzle22 got a reaction from Wanderer in Ninza bonanza   
    I just tried out the new version and it works well. Thank you.
     
    Here is my test of just passing through the plot: https://www.sendspace.com/file/7hmdma
  11. Like
    ⭐ JDizzle22 got a reaction from ⭐ bomdila in Please help, NT7 Indicators taking too long   
    When I run into issues like this, I take the opportunity to clean up my ninja. I remove all (except the ones that came with ninja) my indicators/strategies to a separate folder, remove all my dll's, restart, compile, and then see if the issue is gone. I then add back only the things I know I use. It is painful to do it, but I am always better off when I go through that process (I have only done it a few times).
     
    If you don't want to do all that, it may be a custom DLL, or you can also try clearing your db folder (you will lose all your settings if you delete the sdf, but sometimes that causes problems too).
  12. Like
    ⭐ JDizzle22 got a reaction from ⭐ santoshv2k in Please help, NT7 Indicators taking too long   
    When I run into issues like this, I take the opportunity to clean up my ninja. I remove all (except the ones that came with ninja) my indicators/strategies to a separate folder, remove all my dll's, restart, compile, and then see if the issue is gone. I then add back only the things I know I use. It is painful to do it, but I am always better off when I go through that process (I have only done it a few times).
     
    If you don't want to do all that, it may be a custom DLL, or you can also try clearing your db folder (you will lose all your settings if you delete the sdf, but sometimes that causes problems too).
  13. Like
    ⭐ JDizzle22 got a reaction from ⭐ ESVepara in Please help, NT7 Indicators taking too long   
    When I run into issues like this, I take the opportunity to clean up my ninja. I remove all (except the ones that came with ninja) my indicators/strategies to a separate folder, remove all my dll's, restart, compile, and then see if the issue is gone. I then add back only the things I know I use. It is painful to do it, but I am always better off when I go through that process (I have only done it a few times).
     
    If you don't want to do all that, it may be a custom DLL, or you can also try clearing your db folder (you will lose all your settings if you delete the sdf, but sometimes that causes problems too).
  14. Like
    ⭐ JDizzle22 got a reaction from Nukem in Please help, NT7 Indicators taking too long   
    When I run into issues like this, I take the opportunity to clean up my ninja. I remove all (except the ones that came with ninja) my indicators/strategies to a separate folder, remove all my dll's, restart, compile, and then see if the issue is gone. I then add back only the things I know I use. It is painful to do it, but I am always better off when I go through that process (I have only done it a few times).
     
    If you don't want to do all that, it may be a custom DLL, or you can also try clearing your db folder (you will lose all your settings if you delete the sdf, but sometimes that causes problems too).
  15. Like
    ⭐ JDizzle22 got a reaction from newbie0101 in Please help, NT7 Indicators taking too long   
    When I run into issues like this, I take the opportunity to clean up my ninja. I remove all (except the ones that came with ninja) my indicators/strategies to a separate folder, remove all my dll's, restart, compile, and then see if the issue is gone. I then add back only the things I know I use. It is painful to do it, but I am always better off when I go through that process (I have only done it a few times).
     
    If you don't want to do all that, it may be a custom DLL, or you can also try clearing your db folder (you will lose all your settings if you delete the sdf, but sometimes that causes problems too).
  16. Like
    ⭐ JDizzle22 got a reaction from ⭐ goldeneagle1 in Need auto strategy made from Ninja Indicators, who can take this job here?   
    I've looked at a lot of those and the quality (for a more complex strategy) is really just not that good compared to something you can pay someone to do (I would suggest a Ninja Consultant). I have paid for their framework and I was in no way unimpressed--it is well worth it if you have a somewhat complex system. When you can get overfilled, underfilled, or jumped over in the market, especially fast ones, the free stuff doesn't seem to handle non standard situations all that well and if you plan to use real money with your strategy just pay for it once and then use the framework for your less complicated systems going forward. If you don't want to do that, you may want to take some time to look through this as an alternate framework: https://www.bigmiketrading.com/elite-automated-ninjatrader-trading/15563-njamc-local-order-manager-lom-collaboration.html
  17. Like
    ⭐ JDizzle22 got a reaction from ⭐ Meow in Auto strategy evaluation   
    I think the second paragraph, good points (except win rates), but I fall into the category of not liking profit factors, or win rates because people tend to not really know the "correct" way to interpret such information--just like people don't agree on martingale strategies, IRR vs NPV (historical example as I think most people agree on this now), people will never agree on this. So, a much simpler way to look at it: I look at dollars and what my maximum risk is and if I am willing to accept it (max draw down). Example, I am willing to have a max draw down of 10 points on the ES per contract, but I want to make, on average (minimum) 2 points per trading day on the ES (not a metric displayed in Ninja). If my strategy meets those criteria then I will forward test it (see the second paragraph from rondonelli)--like rondonelli said, make sure you setup commission in Ninja when you forward test and also set the slippage when you run your strategy. When I backtest CL I set slippage to 2 ticks and for ES I set it to 1 tick.
     
    The next thing I would do, and this part is very time consuming, is to look back at your trades in the Chart view and try to determine if any trades were taken during news events, or times when the market moved extremely quickly (if you use range bars you will see this as gaps in range bars and the range bars will have shaved tops and bottoms (several in a row)). If those scenarios occurred, you probably would not have gotten filled, or you would have been slipped, or the market went passed you, came back to your entry and now you are in a losing situation, so you need to then try and manually adjust your strategy results based on any of that. The other thing I look at is the days of week that my strategy is most profitable. Example: I know that one of my strategies does not work the best on Friday, but I have figured out that I can let it trade once before 11AM on Friday, but after that, or if it does not take a trade before then, the strategy turns off.
     
    There is always a debate about win rates, so if you want to go that route, you should look at expectancy (http://systemtradersuccess.com/rank-your-trading-system-with-expectancy-score/). In any case, there will come a point in time if you do run it in the live market that you may need to make the decision to turn off the strategy for good, but hopefully by that time you have made more money than you lost.
     
    I personally used to trade discretionary, but I switched over to 95% automated (ES and CL)--the 5% non-automated is when I am turning on or off my strategy because of news, or big days, like today, when there are multiple major releases that have the ability to make the market move that won't work with my strategy.
  18. Like
    ⭐ JDizzle22 reacted to rondonelli in Auto strategy evaluation   
    I have evaluated more than fair share of strategies for ninjatrader so I am in good position to evaluate. First you should aim for profit factor more than 2 for sure, beware ninja calculated profit factor does not take into account commissions but it takes slippage in consideration though so you should check it with atleast two ticks slippage. Slippage and commissions can destroy any strategy.
     
    You should check on data for couple months in the beginning then forward test it, for instance run test from january to march and then march to april etc. There are months when volatility is high such as January is almost always very volatile that dies down in february. Pay attention to if your strategy is more profitable on long side or short side, yours is better on short side so may think about shorts only etc. Average winning trade should be atleast twice the loosing trade. I like winning rate to be more than 50%, close to 60% is awesome.
  19. Like
    ⭐ JDizzle22 reacted to JoeWilson in Auto strategy evaluation   
    Average Trade $53.24. Is low that means when you average all trades you only make 5 1/3 ticks per trade. This is very low. Max Drawdown $2680 this is bad, this means that at some point in the trading the account lost money all the way down $2680, before it started to recover. In order to trade this with real money, you would need the Minimum Margin Plus $2680 assuming that the Max Drawdown did not increase in the future. It is my opinion that this Strategy as is...is very Risky.
  20. Like
    ⭐ JDizzle22 reacted to admis in Auto strategy evaluation   
    Just my 2 cents to add. When you making a backtest in the Strategy Analyzer based on a very popular Renko family bars - it's critical to remember not only about the slippage but also about the "Fill type". Ninja in SA opens the new order on Open of the next bar (not on the Close of current bar). Implications are obvious. For most renkos the Open is fake, so the same will be a profit in the Strategy Analyzer...
  21. Like
    ⭐ JDizzle22 got a reaction from admis in Auto strategy evaluation   
    I think the second paragraph, good points (except win rates), but I fall into the category of not liking profit factors, or win rates because people tend to not really know the "correct" way to interpret such information--just like people don't agree on martingale strategies, IRR vs NPV (historical example as I think most people agree on this now), people will never agree on this. So, a much simpler way to look at it: I look at dollars and what my maximum risk is and if I am willing to accept it (max draw down). Example, I am willing to have a max draw down of 10 points on the ES per contract, but I want to make, on average (minimum) 2 points per trading day on the ES (not a metric displayed in Ninja). If my strategy meets those criteria then I will forward test it (see the second paragraph from rondonelli)--like rondonelli said, make sure you setup commission in Ninja when you forward test and also set the slippage when you run your strategy. When I backtest CL I set slippage to 2 ticks and for ES I set it to 1 tick.
     
    The next thing I would do, and this part is very time consuming, is to look back at your trades in the Chart view and try to determine if any trades were taken during news events, or times when the market moved extremely quickly (if you use range bars you will see this as gaps in range bars and the range bars will have shaved tops and bottoms (several in a row)). If those scenarios occurred, you probably would not have gotten filled, or you would have been slipped, or the market went passed you, came back to your entry and now you are in a losing situation, so you need to then try and manually adjust your strategy results based on any of that. The other thing I look at is the days of week that my strategy is most profitable. Example: I know that one of my strategies does not work the best on Friday, but I have figured out that I can let it trade once before 11AM on Friday, but after that, or if it does not take a trade before then, the strategy turns off.
     
    There is always a debate about win rates, so if you want to go that route, you should look at expectancy (http://systemtradersuccess.com/rank-your-trading-system-with-expectancy-score/). In any case, there will come a point in time if you do run it in the live market that you may need to make the decision to turn off the strategy for good, but hopefully by that time you have made more money than you lost.
     
    I personally used to trade discretionary, but I switched over to 95% automated (ES and CL)--the 5% non-automated is when I am turning on or off my strategy because of news, or big days, like today, when there are multiple major releases that have the ability to make the market move that won't work with my strategy.
  22. Like
    ⭐ JDizzle22 got a reaction from newbie0101 in R@!ndow   
    I just ran across this utility today and have been messing around with it this morning, so I don't know how well it works in real-time (if it slows your computer), but the developer said he created it with efficiency in mind (http://www.ninjatrader.com/support/forum/showpost.php?p=400531&postcount=1).
     
    Here are the features:
    1. Improved cursor
    2. Enhanced trade visualization
    3. Improved ruler
    4. Indicator configuration templates
    5. Improved databox ... (I still have to work on this one)
    6. Single-key shortcuts on chart (a,b,c,d ... 1,2,3,4, etc.)
    7. Customizable timeframe switches
    8. Synchronized scrolling of charts
    9. Workspace switching by hotkeys
    10. Vertical grid-lines with specified minute interval on intraday chart
    12. Chart style improvements
     
    It's free (no affiliation): http://rainbow-in.com/
     
    When you load it on a chart, just load the indicator "Rainbow" and it will add a toolbar to your chart. There are also other settings you can set in the main indicator window.
     
    The main things that I like on it are:
    1. Plotting prior trade executions is head and shoulders better than the Ninja method
    2. The date and time shows you the actual date with the time, so when manually backtesting, you don't have to search for time to cross the 24/7 line to show you the date
    3. The cursor is a vast improvement over the Ninja--it is crosshaired with price next to the cursor
    4. The shortcut setup in the indicator panel is just awesome.
     
    I only wish they had an option to remove their branding from the bottom two corners, although small, I would rather not see it down there since they already have their logo in my toolbar.
  23. Like
    ⭐ JDizzle22 got a reaction from yunakhan1 in Ninza bonanza   
    I just tried out the new version and it works well. Thank you.
     
    Here is my test of just passing through the plot: https://www.sendspace.com/file/7hmdma
  24. Like
    ⭐ JDizzle22 reacted to ninZa in Ninza bonanza   
    Great JDizzle!
    It's my pleasure :)
     
    Just a short code but it shows that you program very very well :D
  25. Like
    ⭐ JDizzle22 got a reaction from ninZa in Ninza bonanza   
    I just tried out the new version and it works well. Thank you.
     
    Here is my test of just passing through the plot: https://www.sendspace.com/file/7hmdma
×
×
  • Create New...