Can you please show me a screenshot of the Node.js app right after you start it up again. This should be after the data is already in the database. Once your database is loaded, there is no need to populate it again. Then just attach the indicator with load_data set to false to test for arrows anytime after the end_time.

It’s just easy to install the XAMPP.. hehe
I figured this would be the easiest approach for many. NoSQL type DBs have its advantage and disadvantages as well though. For Forex type data I think SQL type DB is what we need. DB speed haven’t become an issue for me yet however. It’s mostly the CPU limits that I’m hitting since the data just gets…[Read more]

Hi Saver0, Why you dont use nginx or sqlite or nosql?
I see them lighter than Apache and MySql.

This is how my screen looks before and after i attached the Fractals Arrow Indicator. There is communication between MT4 and mysql. My database is populated.
But no Fractal Arrow is showing on my screen.

Hello SaveO, here is my screen shot. I am still wondering why it is not showing arrow. Thank you for your time and effort.

Awesome!! Very happy to have another coder work on it

I want to let you know that the MT4 part, I was testing out a few things and the state it’s in is not ideal. Like the way it figures out the current fractal/zigzag pattern before sending it to Node.js app may not be correct. There could be couple of things you could do to do…[Read more]

Awesome!! Very happy to have another coder look at it.

I want to let you know that the MT4 part, I was testing out a few things and the state it’s in is not ideal. Like the way it figures out the current fractal/zigzag pattern before sending it to Node.js app may not be correct. There could be couple of things you could do to do something better…[Read more]

Do we have any coders that understand the Node.js/MQL4 code I have written to be able to try this out?
I probably won’t have time to switch on my brain to do fractals stuff for at least another week or two.

Glad to see that you got it running. What do you see on the Node.js app?
When you post screenshots, please make sure that you post that as well.
Did you see the sets being created and the calculations for each new bar?

Hi everybody,

don’t want to speak for GG, but I have it confirmed by him that real-time bars are sliced by ATR(5) and then are compared against UNsliced history bars.  Attached is a simple indicator that shows how many times each bar shoud be counted for.

Hope it helps.

Vlan

I don’t think we should use ATR to split the candles because the ATR I think will cause mismatches with the history. The candles should be I think be split based on the average bar size of the entire dataset instead. But we can try each one. It shouldn’t be too difficult to test each case 

How should we go about ” “slice” big-bars and make sure not to include fractals among the slices”.

If the bar is lets say 10pips in height (up bar), how should we split it up?

Thanks!

Hi Pedma,

Regarding your point (a) ,  I think GG does not change anything to DB. The gaps handling and splitting the bars is done in his algo …

Saver,

1. No, DB is as it was before. I was lazy to do it during testing differences.. and I already had the Close price in DB. So modifications to the algo seems simpler. in retrospect: a mistake…

2. Same as #1 –

3. Just “slice” big-bars and make sure not to include fractals among the slices.

G.

Ohhh, here we go again…

Stinky, there is no EA per your “requirements”, and there will be no “proof” for claims that wasn’t made.

There is an indicator that does what it shows.

Most of the charts posted are at end of session, so you can match last prediction with whatever came next. Very simple task for you, I’m sure.

If you don’t have…[Read more]

Looks great GG!

Thanks for posting these screenshots.

I have a few questions.

Are your fractals DB now based on closed price fractals?
Did you clean out the data to remove any gaps (weekend gaps, general price gaps)?
Is there anything else that we need to do to prepare the data?

Thank you!