Problem with esignal datafeed.

Questions about MultiCharts and user contributed studies.
waldem
Posts: 108
Joined: 18 Nov 2013
Has thanked: 3 times
Been thanked: 4 times

Problem with esignal datafeed.

Postby waldem » 03 Oct 2014

Hallo MC team,

i have a severe problem using esignal as datafeed.

i'm using weekly bars and i really cannot understand why my strategy cannot recognize the last bar even if the market is close.

today is October 03 and if i plot on chart a very simple code:

Code: Select all

var:MyDate (0);

//Debug
if currentbar = 1 then cleardebug;

MyDate = datetojulian (Date);

print (datetostring (MyDate) ," ", close ," " );
i got the information that the last bar is September 26.

maybe should i open one BUG tracker?
Attachments
powerlanguage.jpg
(398.55 KiB) Downloaded 1179 times

waldem
Posts: 108
Joined: 18 Nov 2013
Has thanked: 3 times
Been thanked: 4 times

Re: Problem with esignal datafeed.

Postby waldem » 03 Oct 2014

I forgot to tell you that i'm using Adidas correctly plot in chart, you can see the picture.
Attachments
ADIDAS.jpg
(248.97 KiB) Downloaded 1176 times

flomtl
Posts: 6
Joined: 23 Jan 2014
Location: Montreal
Has thanked: 3 times

Re: Problem with esignal datafeed.

Postby flomtl » 03 Oct 2014

using weekly bars the last full bar on your chart would be last Fridays close.

the week will close today at 430 and u should then see the Oct3 as the date.

The bar is only considered once its completed.

when u refer to "close" in your code, it is "close" of the most recent bar. since the week hasnt ended, the "close" data is unavailable.

i hope this helps

i think your data feed is ok.

try with a smaller time increment (daily) and see if u get same results.
with daily data the date that should get printed is Oct2
with minute data you would get Oct3.

User avatar
bensat
Posts: 331
Joined: 04 Oct 2014
Has thanked: 46 times
Been thanked: 104 times

Re: Problem with esignal datafeed.

Postby bensat » 04 Oct 2014

...... try with a smaller time increment (daily) and see if u get same results.
with daily data the date that should get printed is Oct2 with minute data you would get Oct3.
Or select "Update On Every Tick" which has further impact on your "print"-statement.

waldem
Posts: 108
Joined: 18 Nov 2013
Has thanked: 3 times
Been thanked: 4 times

Re: Problem with esignal datafeed.

Postby waldem » 04 Oct 2014

Hi fomtl, i wrote the post when the week was finish and the bar already close, i'm writing in European time.

if i put again the system today that is saturday, the week is close and i cannot get the last close, this is an error in my opinion.
if i use metastock data it works.

dear MC developer, as wrote today is saturday and the bar is close.
if i use daily frame i got 03 october, if i use weekly bar i got 26 September.

this problem is not depending from datafeed, also using multicharts datas is the same.

this make no sense in my opinion.

waldem
Posts: 108
Joined: 18 Nov 2013
Has thanked: 3 times
Been thanked: 4 times

Re: Problem with esignal datafeed.

Postby waldem » 05 Oct 2014

Hallo Bensat, i cannot do Update On Every Tick because is a strategy not indicator.

Hallo all, today is sunday and i still cannot get the last friday close, this should be an error.
pls see in attached picture the date of my pc.

on monday i will contact MC developer on chat.
Attachments
error.png
(952.28 KiB) Downloaded 1164 times

waldem
Posts: 108
Joined: 18 Nov 2013
Has thanked: 3 times
Been thanked: 4 times

Re: Problem with esignal datafeed.

Postby waldem » 06 Oct 2014

now is monday morning, new week bar is open and finally i can get the close of October 03, this is amazing....

User avatar
Henry MultiСharts
Posts: 9132
Joined: 25 Aug 2011
Has thanked: 1260 times
Been thanked: 2929 times

Re: Problem with esignal datafeed.

Postby Henry MultiСharts » 06 Oct 2014

We are currently analyzing this behavior.

User avatar
Henry MultiСharts
Posts: 9132
Joined: 25 Aug 2011
Has thanked: 1260 times
Been thanked: 2929 times

Re: Problem with esignal datafeed.

Postby Henry MultiСharts » 08 Oct 2014

This issue has been confirmed. It will be resolved in MultiCharts 9.1.


Return to “MultiCharts”