This is a mobile optimized page that loads fast, if you want to load the real page, click this text.

AmiBroker Tips and Tricks

Jump to new
I think that we all have found that a system tested too good to be true sometimes and a quick easy way to look at why is the code check & profile tool as per below.

I recently missed the - symbol in a reference function which gave me outstanding results but when running the code through the checker it flagged my error.

Ref(H,1) entered instead of Ref(H,-1)

Below are some basic steps for you to follow.





Also you can monitor the system blow by blow by using the Bar Replay feature, where you can see the buy / sell shapes being plotted on your chart.

 

Perhaps send a feature request to Amibroker support? Although if you've seen a lot of complaints on AB forums, then perhaps it might be a waste of an email. But worth a shot to see what their reply would be.
 
I wasn't sure if this post should go here, or in a Norgate Data thread. I guess it could go in both.

I had a "play" with accessing the Norgate Data "extras" Fundamental and Metadata functions, and created the attached AFL file. Just run it in the debugger and view the Output window.

I thought I'd post it here in case anyone else would be interested.

I ask a few questions in the program header. If you know the answers, or can suggest improvements to this code, please let me know.

Cheers...
 

Attachments

  • Snippet - Norgate Data Element Processing.afl
    15.5 KB · Views: 28
Drawing Lines on charts, sounds pretty easy but can be frustrating if you want to connect to open price or close price etc. but line snaps to High or Low.

Well easy fix is to turn on snap to price and hold the relevant key down to to connect to O H L C

example

Turn on Snap to Price =

Then select line ( or rectangle etc ) =


Then hold down the 'C' key to connect to relevant close point .


Happy drawing !
 
Good work @Linus van Pelt as this is something that I have not experimented / utilised yet and will have a look at now. To answer one of your questions in the header I have found this.

1): I could not find where the actual field name is listed. For example, how to retrieve "Gold/Australian Dollar Spot Rate", "AU Unemployment Rate", or "Advance/Decline Ratio". If you know, please let me know.​

Try the following mate

Symbols / Groups / Currencies & Currency Indices / XAUAUD

Symbols / Groups / Economic Data & Indices / #AUJOB

Symbols / Groups / Market Breadth Indicator / #ASXADR.au

So plenty of info available for us to play with but just need an application. How to link Fundamental and Technical Analysis togeteher.

Cheers
 
Can someone help me interpret this code?

Code: 
Sell = Cross(Ref(EMA(L,50),-1),C)OR BarIndex()==(LastValue(BarIndex())-1)

I can understand the first part - it's seeing whether yesterday's low was below the 50 period EMA of lows....but I don't understand what the BarIndex part does - and the Amibroker F1 didn't really help me.
 
TraderJimmy said:
but I don't understand what the BarIndex part does
Click to expand...

@TraderJimmy I am guessing that it detects that the stock is no longer trading (delisted)



with Norgate data you do not need to do this (as shown below)


How do I exit a position in a backtest prior to a stock being delisted?

Assuming a trade delay of 1 bar, you need to have an "exit" signal on the second last bar to simulate exiting a delisted stock. This will cause AmiBroker to exit the position on the final day of trading. You also want to avoid entering any new positions during the final 2 days.

OnSecondLastBarOfDelistedSecurity = !IsNull(GetFnData("DelistingDate")) AND (BarIndex() == (LastValue(BarIndex()) -1) OR DateTime() >= GetFnData("DelistingDate") ) ;
OnLastTwoBarsOfDelistedSecurity = !IsNull(GetFnData("DelistingDate")) AND (BarIndex() >= (LastValue(BarIndex()) -1) OR DateTime() >= GetFnData("DelistingDate") );​
 
Wondering if someone can help me - I seem to get inconsistent results with things like added columns in exploration or chart plot/notation. ie. the code I am running doesn't seem to find it's way to the out exploration or charts. The code is often shared from others and I can see their charts displaying properly, so it's unlikely the code.

I'm trialing Amibroker, is this a limitation? Or is there a setting I haven't selected?
 
Another tip that I've had some success with this week. When you're writing or testing a strategy - its good to output your buy/sell conditions and values to the explore columns. That way you verify the triggers for yourself.

I discovered this while testing a strategy, and I couldn't understand why I wasn't getting buy triggers for months on end. So I added columns to the explore output for each of the buy conditions. Then I could check why the buy wasn't being triggered.

To illustrate this, lets say you have:
  1. an index filter which is true or false, based on the market index being in an uptrend.
  2. A buy condition where the close needs to be above the 40 day EMA =of the stock
Add code like this to output values to your explore results.
AddColumn( indexFilter, "Weekly Index filter", 1 );
AddColumn( cond1, "Condition 1", 1 );
AddColumn( EMA ( C, 40), "40 day EMA", 1 );

You can see below that the output lets you see exactly which part of the trigger is and isn't being met.

 
Thanks @TraderJimmy, the columns thing is very helpful.

I have a question with my Amibroker - running the exploration in a test formula I've coded, for some reason it gives me a Buy Signal that's outside of my date range? I.E. Buy signal for 7th August when the Range is set to 1 recent day(s) and The date is 1st Sept to 5th Sept.



FYI
- it is a weekly system, and I ensured that the parameters in the explore setting is weekly,
and that my charts are also in the weekly view
- The Filter is set to All Ordinaries (ASX) from Norgate Data
 
@Nameless_ I have unsuccessfully tried to replicate your issue with a few of my test systems, so without your test formula it is impossible to answer your question.
 
Trav. said:
@Nameless_ I have unsuccessfully tried to replicate your issue with a few of my test systems, so without your test formula it is impossible to answer your question.
Click to expand...

@Trav. Thanks for looking into this - it's essentially a minimally modified version from one of the systems from Skate's Dump It Here thread as I was going through it and trying to learn how to code
 

Attachments

  • Nameless Test Formula.afl
    6.4 KB · Views: 17
@Nameless_ OK, I think that I have found the problem, and I will attempt to describe it below which may be a bit confusing on the first read

In your snip AJM is giving the problem and that is because they have been suspended from trading and their last trading day was the Friday 7/8/2020 which just happen to be a day that generated a Buy Signal in the code

From the ASX announcement page



Now this brings us to the problem of why the Explore results bring up AJM....

I suspect that you have Pad and Align Off in the Analysis Settings as per the default setting and when running the Explore set to 1 recent day it finds that the last recent day for AJM was on the 7/8 as per above.

Now if you use the pad and align feature in AmiBroker you will see that it fills the holes in the data with the last valid previous data.

http://www.amibroker.com/guide/w_settings.html



EXAMPLE on Pad & Align

By changing the Explore Filter to 1 as per below, turning on Pad & Align and then adding some range dates for the test you will see the newly added close column shows 0.07 for the period since AJM was delisted.

Filter = 1;//Buy OR Sell; // Buy & Sell Filters
AddColumn(Close, "Close");





To expand on this test I have included the before and after results when the Pad & Align feature is used.

Before




After





Now in figuring out the above Norgate has a different approach which I have not implemented yet but will do so later today.

https://norgatedata.com/amibroker-faq.php#padandalign



The below lines will are needed for the above to work

#include_once <..\Norgate Data\Norgate Data Functions.afl>;
Condition1 = NorgatePaddingStatusTimeSeries()==0;

Buy = Condition1 AND ...................normal buy conditions

Hopefully the above helps and if anyone else has some thoughts or better way to explain this then please chip in, as I am no expert here.

Cheers
 

Attachments

  • upload_2020-9-6_4-53-48.png
    143.6 KB · Views: 8
  • upload_2020-9-6_5-5-12.png
    12.2 KB · Views: 7
You must log in or register to reply here.

Similar threads

November 2024 DDD
2 3
Replies
53
Views
6K
ducati916
System optimisation: IS training vs. OOS testing, and Paper Trading
Replies
10
Views
2K
Garpal Gumnut
R
Books on Moats & Competitive Advantage
Replies
0
Views
1K
RickyY
R
J
The 'plan'
Replies
5
Views
2K
ducati916
R
A Million Dollars Lesson
Replies
0
Views
808
RickyY
R
Menu
Log in
Register
Cookies are required to use this site. You must accept them to continue using the site. Learn more...