Information

Username: Jiri
Member since: 31 Aug 2015
Last login: 01 Mar 2023
Status: Active

Activity

Where Created Comments
Algorithms 24 47
Forum Topics 31 223
Jobs 1 8

About

Co-Founder & CTO at PoshTrader Ltd with +8 years of trading experience. Providing programming services and a marketplace where you can buy and sell addons for trading platforms - www.poshtrader.com

Last Algorithm Comments

Jiri's avatar
Jiri Beloch · 3 years ago

https://docs.poshtrader.com/products/installation#ctrader-indicators-cbots

All indicators and cBots require unlimited access rights to communicate with our servers - validate your license, check for latest releases and updates.

Jiri's avatar
Jiri Beloch · 3 years ago

My apology, marking as paid. However, you can try it completely free for 7 days. Just download and give it a try!

Jiri's avatar
Jiri Beloch · 5 years ago

Thanks for pointing this out, didn't notice it. :)

Jiri's avatar
Jiri Beloch · 5 years ago

The Renko is overlaying your chart, it's just an indicator. Since the chart is time-based while Renko is price-change based there is applied a logic that shifts Renko to align with the latest bar. You will need to integrate same logic to the indicator if you want to feed it with Renko as a source.

Jiri's avatar
Jiri Beloch · 6 years ago

It's not a bug, that's how classic/standard renko is supposed to work as explained in previous comments. If you want to protect your position just set SL to same size as a renko brick and trail it.

I am planning to release an universal renko which can be optimized to your needs - brick size, open offset and reversal size, as soon as we publish our website.

Jiri's avatar
Jiri Beloch · 6 years ago

Hi, contact me directly via email. Thanks.

Jiri's avatar
Jiri Beloch · 6 years ago

No offence but you have literally copy-pasted my daily fibo indicator and now selling it as a part of your indicator. You should at least give some credits.

https://ctrader.com/algos/indicators/show/1101

Jiri's avatar
Jiri Beloch · 6 years ago

I would agree with you but we would be both wrong. I tried hard to explain you why is your calculation wrong - it's 1 bar/tick (even t1 chart has OHLC values but call it however you want) delayed, the result of current bar is not calculated at all instead it holds value for previous bar.

For those that are interested in what it's all about: Proper Version

Jiri's avatar
Jiri Beloch · 6 years ago

I am not going to explain anything to you. You clearly have no idea how my version of the indicator is working and you are not willing to accept your error. Compare results if you dont trust me but don't expect me to waste more time trying to help you. Please stop talking nonsense if you can't even prove it.

Jiri's avatar
Jiri Beloch · 6 years ago

I have noticed that OpenTime of MarketSeries usually returns slightly future time which makes no sense and its broker related (I suppose). That's why it might return negative value, however I kept the calculation logic same to yours so it's fixed at the close of the bar.

http://i.imgur.com/0m7BpRM.png

Jiri's avatar
Jiri Beloch · 6 years ago

I’ll try being nicer, if you try being smarter.

Milliseconds Elapsed Proper Version

Jiri's avatar
Jiri Beloch · 6 years ago

Of course it's like that, the Calculate method is called on each price change with its index. Are you so dumb not to understand core logic? If it's attached on tick chart it's going to be called on each new bar, how can you possible know the close time of that candle if it wasnt closed yet. Make it update each millisecond if you want to keep setting values for current index. I am done talking to you, such a waste of time.

Jiri's avatar
Jiri Beloch · 6 years ago

Sorry, the log was order by message. This one is ordered by time so you can clearly see its shifted.

http://i.imgur.com/PzAMGxD.png

Jiri's avatar
Jiri Beloch · 6 years ago

Yes, you are right, I didn't need to download your indicator in order to see it's not working properly because I can read the code and I understand the logic unlike you. Anyway, I have downloaded your indicator and made it print some data on each tick, attached to t1 chart and what a surprise, I was right and you were wrong.

http://i.imgur.com/UQSwjQX.png

Jiri's avatar
Jiri Beloch · 6 years ago

Yes, it is shifted. Open time of previous bar subtracted from open time of current bar is not equal of elapsed time for current bar, don't you understand that?

Do you even know who is a troll? I guess you are referencing to this algo where I was talking about the transparency of the robot how it abuses negative spread. It made me mad that someone is selling that kind of robot (especially if he calls it "holy grail") even when he knows it's not going to be profitable in real market conditions at all. If I was trolling at first place I would still be arguing with that person.

I have explained your error in detail and you just keep saying it's not true and instead you call me a troll.

If you have seen me before that you know I am helping people on this website, not trolling.

With all due respect, go fuck yourself.

Jiri's avatar
Jiri Beloch · 6 years ago
For same reason as for t1 chart? Before the edit you havent stated that its for t1 chart only. Still the result is shifted by one bar so its technically not working properly.
Jiri's avatar
Jiri Beloch · 6 years ago

Yes, I did read that you use it for T1 chart and I can imagine it's not a big deal having results shifted 1 bar back especially if you are using line chart and not being able to see result for current bar. However, since you making it public someone would want to use it on different timeframe (T34 for example) where it would not be showing correct results.

Jiri's avatar
Jiri Beloch · 6 years ago

Hi, your calculation isn't righ - Elapsed[index] returns milliseconds elapsed of previous candle (index - 1) not the current candle. The calculation you have should be used for historical data (!IsRealTime) and assigned to Elapsed[index - 1] so you have history calculated as well. In my opinion the histogram should be visible from 0 value, you should consider using another output as zero level instead of using chart objects so the indicator is forced to resize the window correctly. Additionally you can use TimeSpan.TotalMilliseconds property instead of your custom method.

To calculate how many milliseconds have elapsed current bar:

if (IsRealTime)

{

   Elapsed[index] = Time.Subtract(current).TotalMilliseconds;

}

Jiri's avatar
Jiri Beloch · 6 years ago

Are your other robots based on negative spread as well?

Jiri's avatar
Jiri Beloch · 6 years ago

What's the purpose of posting such a robot? If it's for education porpose why don't you upload the algo file with the source code here so we can actually learn something about it? Why does it require full permission?

Jiri's avatar
Jiri Beloch · 6 years ago

Additionally the algo requires full permission for no reason. I would love to know why. :)

Jiri's avatar
Jiri Beloch · 6 years ago

After seeing this I highly recommend staying away from KRATX. This kind of algorithm is just abusing negative spread in the historical data. Live trading this particular strategy would lead to guaranteed instant loss.

Jiri's avatar
Jiri Beloch · 6 years ago

Hi, here you go. http://pastebin.com/embed_iframe/EAk442yZ

Jiri's avatar
Jiri Beloch · 6 years ago

Hi, you need to install the SwingZigZag indicator.

Jiri's avatar
Jiri Beloch · 6 years ago

This indicator is meant to be used for intraday trading and it's limited to 1440 minutes (1 day) because it resets on each new day. How would you want to seperate 100 days? Where should it start counting days? On first bar on the chart or first day of the year?

Jiri's avatar
Jiri Beloch · 7 years ago

Thank you for the report. Fixed.

Jiri's avatar
Jiri Beloch · 7 years ago

Would be nice to see both selling and buying volume separated. Maybe 2 histograms, above 0 for buy and below for sell. Anyway, great idea! Thanks for sharing. :)

Jiri's avatar
Jiri Beloch · 7 years ago

There is Indicator Attribute called AutoRescale which indicates whether the instance automatically rescales the chart or not. It's set to true by default but you can turn it off.

[Indicator(AutoRescale = false)]

Jiri's avatar
Jiri Beloch · 7 years ago

Can't build it without the Heiken Ashi indicator. May you provide link to the indicator as well?

Jiri's avatar
Jiri Beloch · 7 years ago

Does Sydney open at 9pm utc? If so, I had it wrong in the code. Fixed version uploaded.

Jiri's avatar
Jiri Beloch · 7 years ago

Does the vertical line showing your local time correctly?

Jiri's avatar
Jiri Beloch · 7 years ago

There was a bug in offset, which might caused the issue. Please, try it now and let me know if it works.

Jiri's avatar
Jiri Beloch · 7 years ago

I don't see any problem.

Jiri's avatar
Jiri Beloch · 7 years ago

I cleaned up the code. Try it now.

Jiri's avatar
Jiri Beloch · 7 years ago

@majesamade What problem exactly?

Jiri's avatar
Jiri Beloch · 7 years ago

Could you send me a screenshot on mail: belochjiri@hotmail.com, please? I am unable to replicate this behavior on my end.

Jiri's avatar
Jiri Beloch · 7 years ago

Did you download the algo or copied the source code above? The code above is full of messed up characters.

Jiri's avatar
Jiri Beloch · 7 years ago

@marciogarcia : As I stated in "Accuracy" above, when the indicator is loaded it can access only OHLC values of historical data. So if you left indicator running a while, it got fed by tick data and might plot some candles that you can't read from OHLC values only. When you refreshed the chart those candles may disappeared due to lack of data.

Jiri's avatar
Jiri Beloch · 7 years ago

It repaints if there is new swing of last direction, but once there's Zig-Zag it won't repaint. :)

Jiri's avatar
Jiri Beloch · 7 years ago

What you mean by nothing happened? Did you put it on your chart as any other custom indicator?

Jiri's avatar
Jiri Beloch · 7 years ago

@trend_meanreversion: Not really. I was studying renko on multiple platforms and they all work just like that. The price needs to surpass the top or bottom of the previous brick by a predefined amount in order to make new brick.

Otherwise, the chart would like something like that.

  •    ⍁⍂
  • ⍁      ⍂

Instead of.

  •    ⍁
  • ⍁   ⍂
Jiri's avatar
Jiri Beloch · 7 years ago

@trend_meanreversion I guess you were talking about another issue I came across today and fixed. Please download updated version. ;)

Jiri's avatar
Jiri Beloch · 7 years ago

@trend_meanreversion Thank you for reporting that issue. Outputs are fixed now and Open/Close.LastValue should return value now.

Jiri's avatar
Jiri Beloch · 7 years ago

Please, download latest version for better performance. ;)

Jiri's avatar
Jiri Beloch · 7 years ago

I haven't tried this indicator but doesn't it spam emails with each tick when higher than defined volatility?

Jiri's avatar
Jiri Beloch · 7 years ago

Does it still work?

Last Jobs Comments

Jiri's avatar
Jiri Beloch · 6 years ago

Hi, do you still need this to be done?

Jiri's avatar
Jiri Beloch · 6 years ago
Hi, I am available to do the job. Send me your requirements on email address belochjiri@hotmail.com and I will get back to you with estimated time for completion. Best regards, Jiri
Jiri's avatar
Jiri Beloch · 7 years ago

Hello jhtrader,

I am just wondering, did you find errors in ZigZag indicator written by me? If so I will be more than happy if you tell me about them so I can fix it.

 

Also if you are still looking for someone to do the job, feel free to contact me.

 

Best regards,

George

Jiri's avatar
Jiri Beloch · 7 years ago

Hello. 

Please, contact me via email: belochjiri@hotmail.com :) 

 

Best regards, 

George

Jiri's avatar
Jiri Beloch · 7 years ago

Hi,

Contact me by email.

 

Best regards,

George

Jiri's avatar
Jiri Beloch · 7 years ago

Hi,

Please contact me, email: belochjiri@hotmail.com

 

Best regards,

George

Jiri's avatar
Jiri Beloch · 7 years ago

Hi,

Please contact me: belochjiri@hotmail.com

 

Best regards,

George

Jiri's avatar
Jiri Beloch · 7 years ago

Hello,

I can do it. Please, contact me on email: belochjiri@hotmail.com

 

Best regards,

George B.