Recent Posts

Pages: [1] 2 3 ... 10
1
Beyond Charts / Re: how to work out which sector is outperforming?
« Last post by JohnR on 16/06/2019, 03:26:35 PM »
Hi Campbell,
I note that the RSC Profile Period Type is set to Level:Market and Period Type:Week.

For the above posted RSC 'Sector' scan is set to Day by default when created; my question is should the new scan Parameters for RSC Sector under also reflect the scan profile of Period Type:Day as it defaults to week?

I'll be checking this every day as per the Indexes Risk scan, and scans from the same workspace tab group.
2
Beyond Charts / Re: Help with BCFL custom Scans & Coding
« Last post by JohnR on 14/06/2019, 05:47:14 PM »
Is it possible to apply an output with: line, or histogram, or colour to an output entity?
3
General Discussion / Chit Chat / Interactive Brokers
« Last post by Don McKinnon on 14/06/2019, 05:42:54 PM »
Hi everyone,

The US based broker, Interactive Brokers, now operates in Australia and some of major problems that local investors have had with it in recent years no longer exist.  New Austalian clients can now set up accounts for their SMSFs and IB's low brokerages on US market trades are available for new local clients.  Also, the extremely frustrating anti free-riding rules that used to apply to US based clients don't apply to the Aust accounts.  Importantly the Help Desk is now also Australian based during its local working hours with after hours support still based in the US.

IB also executes trades on other markets  It's ASX brokerages are not a low as those of Self Wealth.

All Australian based clients that had the previous US based accounts were transferred to the new Ausralian entity earlier in the year.

It's worth having a look at if you're looking for a new broker for US trades .... https://www.interactivebrokers.com.au/en/index.php?f=39753&p=stocks1

Regards
Don

4
Beyond Charts / Re: Help with BCFL custom Scans & Coding
« Last post by Campbell Sinclair on 12/06/2019, 03:06:33 PM »
Hi John,

The base language it is based off does not have this capability either, the functionality you are looking for just goes a little bit beyond what these languages do until we can naturally extend its base capabilities.

For what you have asked - look at the right hand side BCFL Library. This is a list of all the functions in BCFL and there's a dedicated indicator section.

Highlight the top indicator, then open the quick reference section (the book icon with the thunderbolt) at the top of the panel. This is the documentation for the indicators and it gives examples of what each function requires to operate.

An indicator with the DATA ARRAY syntax can take other indicators as an input to the calculation. This is also a great place to look to see how functions work when you come back to formulas in the future.
5
Beyond Charts / Re: Help with BCFL custom Scans & Coding
« Last post by JohnR on 12/06/2019, 12:27:55 PM »
Hi Campbell,
If the RSI is broken for BCFL I am wondering about using another indicator to take the MACD histograms data.

Are you able to list the BC indicators that will take another indicators values like the RSI and MACD to be used in BCFL?

Thanks.
6
Beyond Charts / Re: Help with BCFL custom Scans & Coding
« Last post by Campbell Sinclair on 06/06/2019, 03:51:54 PM »
No not really - as the RSI is in effect a 2 part calculation, and inputs to the final calculation are updated differently depending on how the price action moves. This cannot be easily replicated in the style of language that BCFL is.

SQRT() and ROUND() are both Math functions that can be accessed in BCFL, which will provide senisble output given the input in to either is a number.

ie. SQRT(Round(20.5)); will give back 4.47.
7
Beyond Charts / Re: Help with BCFL custom Scans & Coding
« Last post by JohnR on 06/06/2019, 12:53:52 PM »
Thanks for the formula.

Quote
Volume depth for orders or liqudity at certain price points and the importance should be reconciled with the risk of waiting on the sidelines.
Yes, am beginning to see this through practical experience; held IAG for this very reason (in fact a few stocks with thin buy sides), This is what is prompting me to use Trading View's intra-day time frames to spot any turning points, although it multiplies my workload.

I guess this is what happens when you get multiple trading systems all triggering sells at the same time = a rush for the exit doors! the herd following rules can alone move a stock considerably downward. Although IAG still in underlying trend I do expect from being so severely oversold a correction of sorts.


I have a question in regards to porting the Hull MACD over to BCFL and was wondering if the same RSI limitation in BCFL might effect this indicator (p.s. don't spend too much time on this):
Where round and sqrt = attached images. And obviously minus the plot lines.

{ ---- HULL MACD 1 ---- }
f_hma(_src, _length)=>
    _return = wma((2 * wma(_src, _length / 2)) - wma(_src, _length), round(sqrt(_length)))

len_fast1 = input(120, "Fast MA", minval=1)
len_slow1=input(260, "Slow MA", minval=1)
len_sig1=input(90, "Signal Length", minval=1)

fast_ma1 = f_hma(source, len_fast1)
slow_ma1 = f_hma(source, len_slow1)

MACDM1 = fast_ma1 - slow_ma1
MACDS1 = wma(MACDM1, len_sig1)
MACDH1 = MACDM1 - MACDS1

plot(MACDH1, style=histogram, linewidth=2,color=#2b77f2, transp=10)
plot(MACDM1, color=blue, linewidth=2)
plot(MACDS1, color=red, linewidth=2)

8
Beyond Charts / Re: Help with BCFL custom Scans & Coding
« Last post by Campbell Sinclair on 05/06/2019, 02:51:34 PM »
As long as you have a process outlined!

Volume depth for orders or liqudity at certain price points and the importance should be reconciled with the risk of waiting on the sidelines. We believe it is better to follow the defined exit signals for peace of mind alone than chasing price points, as any system with sufficient edge will reveal itself over time via execution of the process. The process being following the defined entry and exit signals that build towards that reseached edge.

As for the formula, you want the fmrvar() function.

input_A := fmlvar("MACD1", "MACDH1");

and the syntax is:

input_A := fmlvar("Formula Name", "Variable Name in Formula");
9
Beyond Charts / Re: Help with BCFL custom Scans & Coding
« Last post by JohnR on 05/06/2019, 12:50:56 AM »
OK, I'm thinking more along the lines of going long on some of the stronger looking scans and judging the state of the trend for BC daily data within TradingView's intra day time frame; 1 hour seems to work. This works much like a weekly data chart (long entry, exit) with taking signals on the daily data charts (short entry, exit).

The RSI of MACD histograms work well on the intra day charts, so will go with this for now, and it makes picking swing tops and bottoms much easier than relying on basing trades on signals generated on the previous days data, if the signal happened yesterday morning and the TM trade action takes place today at some point, the risk is the sell side on some stocks might look too thin today to place a direct price trade, forcing to sell down several price points to get the bulk of the order filled, or sit on the sell side with fingers crossed. Maybe I can pick the turning point clearer on the 1 hour chart data (see example images).

It will be a juggle to organise rapid turnover that SPA3-T, as well as my own scans, and to manage it all through the portfolio manager, but I've already started to go long on some of the New Entries and other scans ignoring system signals where they occur in strong trends to ride the trend until Moving Average, MACD2 and MACD1 loses momentum.

Re the formula for:
>mentioned in a few posts back was the short form formula:
"This is another formula that gets both of these * individual * formulas and plots their calculations."

{ New Formula }
RSI1 := FML("MACD1");
RSI2 := FML("MACD2");

RSI1;
RSI2;


If the MACD has 3 outputs (as indicator), how do you reference one or two of those outputs where;
saved formula title = MACD1:

{ ---- MACD 1 ---- }
MACDM1:= mov(C, 120, E) - mov(C, 260, E);
MACDS1 := mov(MACDM1, 90, E);
MACDH1 := (MACDM1 - MACDS1);
MACDM1;
MACDS1;
MACDH1;

In short form when calling the title name:

MACD1 := FML("MACD1");

but want a qualifier for MACDH1, MACDS1 and or MACDM1; does th short form automatically read all the outputs to put into the qualifying parameters?

QF1 := MACDM1 > MACDS1;
TRIG_UP := MACDH2 > REF(MACDH2, -1) and REF(MACDH2,-1) < REF(MACDH2,-2);


Thanks.
10
Beyond Charts / Re: Help with BCFL custom Scans & Coding
« Last post by Campbell Sinclair on 04/06/2019, 03:42:23 PM »
We can expand RSI to take parameters as I outlined initially, so that you can choose which data sets the BCFL RSI function is applied to instead of just the close - although this will be down the track once the development team completes their current business projects.

The BCFL Library are the pre-built functions, so it is the RSI in here that would be expanded.
Pages: [1] 2 3 ... 10