|
TickBarSize=null JFException message |
ccadar
|
Post subject: TickBarSize=null JFException message |
Post rating: 0
|
Posted: Sun 02 Mar, 2014, 17:12
|
|
User rating: 3
Joined: Mon 05 Nov, 2012, 11:56 Posts: 80 Location: Germany,
|
Dear Support, If I executed the following line: ITickBar bar= history.getTickBar(Instrument.EURJPY, OfferSide.ASK, TickBarSize.valueOf(200), 0); I get the following error message: 16:03:13 com.dukascopy.api.JFException: Params could not be null: Instrument=EUR/JPY OfferSide=Ask TickBarSize=null @ com.dukascopy.api.impl.util.c.a(Unknown Source) This is happening whenever I set a value grater than 100 tickbars in the TickBarSize.valueOf() input. Could you please let me know how to get history Tickbars of 200 ticks each? Thanks
|
|
|
|
 |
Platform Support
|
Post subject: Re: TickBarSize=null JFException message |
Post rating: 0
|
Posted: Mon 03 Mar, 2014, 10:14
|
|
JForex Master |  |
User rating: ∞
Joined: Wed 16 Sep, 2009, 18:23 Posts: 1054 Location: Geneva, Switzerland
|
This is due to max limit of 100 for the tick bars.
|
|
|
|
 |
ccadar
|
Post subject: Re: TickBarSize=null JFException message |
Post rating: 0
|
Posted: Tue 18 Mar, 2014, 14:32
|
|
User rating: 3
Joined: Mon 05 Nov, 2012, 11:56 Posts: 80 Location: Germany,
|
Platform Support wrote: This is due to max limit of 100 for the tick bars. Hello Support, will Jforex 4 support more than 100 tickbars ? Thanx
|
|
|
|
 |
Platform Support
|
Post subject: Re: TickBarSize=null JFException message |
Post rating: 0
|
Posted: Tue 18 Mar, 2014, 17:55
|
|
JForex Master |  |
User rating: ∞
Joined: Wed 16 Sep, 2009, 18:23 Posts: 1054 Location: Geneva, Switzerland
|
Yes, it will. Current JForex will have it as well soon.
|
|
|
|
 |
ccadar
|
Post subject: Re: TickBarSize=null JFException message |
Post rating: 0
|
Posted: Sun 23 Mar, 2014, 19:49
|
|
User rating: 3
Joined: Mon 05 Nov, 2012, 11:56 Posts: 80 Location: Germany,
|
Platform Support wrote: Yes, it will. Current JForex will have it as well soon. Hello Support, it seems Jforex 4 has the same limitation of 100 tickbars...that's annoying..or am I missing something? 
Attachments: |
tickbars.jpg [70.78 KiB]
Downloaded 746 times
|
DISCLAIMER: Dukascopy Bank SA's waiver of responsability - Documents, data or information available on
this webpage may be posted by third parties without Dukascopy Bank SA being obliged to make any control
on their content. Anyone accessing this webpage and downloading or otherwise making use of any document,
data or information found on this webpage shall do it on his/her own risks without any recourse against
Dukascopy Bank SA in relation thereto or for any consequences arising to him/her or any third party from
the use and/or reliance on any document, data or information found on this webpage.
|
|
|
|
|
 |
Platform Support
|
Post subject: Re: TickBarSize=null JFException message |
Post rating: 0
|
Posted: Mon 24 Mar, 2014, 22:09
|
|
JForex Master |  |
User rating: ∞
Joined: Wed 16 Sep, 2009, 18:23 Posts: 1054 Location: Geneva, Switzerland
|
Expect it to be released soon in both.
|
|
|
|
 |
ccadar
|
Post subject: Re: TickBarSize=null JFException message |
Post rating: 0
|
Posted: Fri 04 Apr, 2014, 12:59
|
|
User rating: 3
Joined: Mon 05 Nov, 2012, 11:56 Posts: 80 Location: Germany,
|
Platform Support wrote: Expect it to be released soon in both. Thanks for releasing it ! One issue I'd still have to comment on. If I compared a jforex 300 tick chart with a prorealtime 300 tick chart I can see, there is a big difference! For the same time interval on the prorealtime chart there are 105 bars (each bar contains 300 ticks) but on jforex there are only 41 bars...where does this difference come from?? Jforex is showing really 300 tick bars? it seems much more...(see screenshots attached).  
Attachments: |
jforex.jpg [142.03 KiB]
Downloaded 397 times
|
proreal.jpg [159.64 KiB]
Downloaded 476 times
|
DISCLAIMER: Dukascopy Bank SA's waiver of responsability - Documents, data or information available on
this webpage may be posted by third parties without Dukascopy Bank SA being obliged to make any control
on their content. Anyone accessing this webpage and downloading or otherwise making use of any document,
data or information found on this webpage shall do it on his/her own risks without any recourse against
Dukascopy Bank SA in relation thereto or for any consequences arising to him/her or any third party from
the use and/or reliance on any document, data or information found on this webpage.
|
|
|
|
|
 |
hyperscalper
|
Post subject: Re: TickBarSize=null JFException message |
Post rating: 0
|
Posted: Fri 04 Apr, 2014, 18:43
|
|
User rating: 98
Joined: Mon 23 Jul, 2012, 02:02 Posts: 656 Location: United States, Durham, NC
|
I don't think it's valid to compare constant tick bars across different data sources or brokerages.
Even within the Dukas brokerage, if you were to create your own tick bars, versus calculating from a historical tick data feed you would have more constant tick bars from the live data source. And you'd also probably get a different result with Demo vs Live. I deal with "ticks" all the time.
Creating tick bars is just basically counting ticks, I believe. And ticks are just "delta" price values on the inside market. So, other than simply telling you how "active" a market is, tick bars are not particularly useful.
The concept of a "tick" is also somewhat variable and flawed. Dukascopy does not show sizes less than $100k on the inside bid/ask. This will influence the number of "ticks" or price changes per unit time which will occur.... as it ignores possible smaller bids/offers.
Maybe I don't understand tick bars... that's possible.
HyperScalper
|
|
|
|
 |
ccadar
|
Post subject: Re: TickBarSize=null JFException message |
Post rating: 0
|
Posted: Fri 04 Apr, 2014, 19:06
|
|
User rating: 3
Joined: Mon 05 Nov, 2012, 11:56 Posts: 80 Location: Germany,
|
hyperscalper wrote: I don't think it's valid to compare constant tick bars across different data sources or brokerages.
Even within the Dukas brokerage, if you were to create your own tick bars, versus calculating from a historical tick data feed you would have more constant tick bars from the live data source. And you'd also probably get a different result with Demo vs Live. I deal with "ticks" all the time.
Creating tick bars is just basically counting ticks, I believe. And ticks are just "delta" price values on the inside market. So, other than simply telling you how "active" a market is, tick bars are not particularly useful.
The concept of a "tick" is also somewhat variable and flawed. Dukascopy does not show sizes less than $100k on the inside bid/ask. This will influence the number of "ticks" or price changes per unit time which will occur.... as it ignores possible smaller bids/offers.
Maybe I don't understand tick bars... that's possible.
HyperScalper if this is true how come that each 1 minute bar are almost identical even on OCHL levels on both charts? 
|
|
|
|
 |
|
Pages: [
1
]
|
|
|
|
|