Datamanager B124 error(s)
hi i have many issue with datamanager B124.
i tryed update all and i got a mistake like in picture 1 for NZDUSD.
in picture 2 we can see strange end date for cloned timezone.
-
Votes +1
-
Project StrategyQuant X
-
Type Bug
-
Status Fixed
-
Priority Normal
History
l
h
hankeys
03.10.2019 18:10
cloning could lead that cloned data will end later - for example 1.10. end data UTC0 - 23:59, in UTC2 it could be 2.10. - 2:59
l
Loonly
04.10.2019 07:14
hankeys not in this case. If you noted i clone from utc tu est07.
It is impossible.
l
h
hankeys
04.10.2019 07:38
whad do you think its impossible - est07 is UTC2/3 by the DST time, so if dukascopy data wil end 23:59, est 07 could end 1:59 or 2:59...take a look at the data itself - use VIEW and ANALYSE
l
Loonly
04.10.2019 07:45
dukas is downloaded in UTC = 0 so it can not END the day later, it is impossible, the max is 20.59
also: please be aware that UNTIL NOT it always updated in the SAME day final - so how do you explain that now it never done such a behavior before?
also: please be aware that UNTIL NOT it always updated in the SAME day final - so how do you explain that now it never done such a behavior before?
Thank you
h
hankeys
04.10.2019 10:57
holy moly UTC 0 time is still till 23:59, you know that?
yes, Friday in UTC0 wil end at 20:59, because of end of trading, but time is still ticking...and UTC0 will have Sunday candle starting at 21:00
i am afraid, that 1.10.2019 is a tuesday, so data will be from 00:00 - 23:59, because of that cloned data +2/+3 will end the next day
TT
Tamas
07.10.2019 10:08Status changed from New to Fixed
Thanks hankeys for your support :)
Problem with unknown logic type was fixed.
l
Loonly
07.10.2019 10:18
i don't understand how you made calculation.
UTC=0 teh data
EST+07 the cloned.
UTC=0 NEVER end later than 20.59 correct?
so if i clone to EST+07 DST+2+3 , MAXIMUM can be 23.59 so it is SAME day.
Votes: +1
© Copyright. All rights reserved. ProjectPanel.com
