Posts made by josecortesllobat

By an iterative process:

1. run an all parameters optimization with long steps for each one (SL-> Init = 10, End = 100, Step = 10)
2. when you get a good strategy´s performance parameters set, start with a single parameter optimization with a short step
3. when you get that the reult for the single optimization parameter is better than before, keep that parameter fixed and run again a multi parameters optimization as for the first step
4. go forward with a new single parameter optimization
5. repeat the iterative method until you get what you think is the best parametrization

Keep in mind that the best optimized parameters set (one giving the highest profit, for example) does not mean that it is the best option to trade.

You have all what is needed in some block like "Formula" one

If you want to calculate the UpperWickPercent in respect of the Candle Total size, you just need to use the "Formula" block

double UpperWickPercent
UpperWickPercent = (Candle upper wick size / Candle total size) * 100

I would say that you need some project branches to get what you are looking for.

bool StopTrade (variable to be modified depending on the conditions)

Branch - 1 -> Conditions to trade will be checked out if StopTrade == false

Branch - 2 -> If a closed trade is a lose, then StopTrade == true

"For each closed trade" with n = 1 (newest to oldest) will load only the last trade closed. If the profit of that last trade is < 0 (lose), then StopTrade == true. With that, the conditions to trade will not be checked out anymore until the variable StopTrade become false.

Branch - 3 -> Reset StopTrade for each new day

That could be an approach. NOT TESTED

Try +2pips instead of 0.2pips

@ambrogio You are correct but it depends on what @Dan-2 wants to get.

From the project shared by @Dan-2,

If "No trade" is running, run true output and place 4 buy pending orders

But if it wants to look at the pending orders as well, it is required an additional block like as follows

If "No pending order" & "No trade" is running, run true output and place 4 buy pending orders

So, it depends on what needs to be met.

@Dan-2

Try this out

@Dan-2

Follow the suggestion given by @l-andorrà.

To avoid opening more trades of that you want, you have to set which trades do you want to look at with the "No position" block

"Group Mode = Group #" looks for the the trades that match with the group number specified. If the field Group # is not filled, there is no trade to look at.

"Group Mode = All" looks for any trade that is currently running.

Not sure if this is what you are looking for but it´s my way

When there is no position running, BarCounter is set to 0 each time a new bar opens.

When there is a position running, BarCounter is set to BarCounter+1 each time a new bar opens.

It works well for me. As usual.

Candle Close (ID = 0) belongs to the bar being formed so that level changes as long as the bar is being formed. It's better to work with closed candles:

If Candle Close (ID = 1) x> BB -> Do something

The indicators also need a candle ID to evaluate the condition.

https://www.mql5.com/es/docs/constants/objectconstants/wingdings

La mejor opción es tener un indicador técnico que te haga el trabajo.

https://www.mql5.com/es/code/12690

Hello @fxDreema

I would like to request if you could be so kind to check the OnDeinit section of the compiled code.

I realize that some expert advisors were removed from the chart where they were running on my broker´s demo account without apparently reason. I looked a the Journal tab and I saw some logs about the EAs removal

http://prntscr.com/ohd0r0

But nothing about the reason why they were removed.

I was looking to implement a way to log the reason for the EAs removal and I found this function

https://docs.mql4.com/constants/namedconstants/uninit

So, I wanted to implement that function to my EAs code but I saw that you have already added it to the compiled projects.

I would say that might be there is a bug because when I removed an EA from its chart, I did not see any log about the reason why it was removed.

Thanks to a suggestion from @miro1360,

https://ctrlv.cz/shots/2019/07/19/Wmr9.png

When an EA is removed from the chart, the terminal sends me an email with the reason code which is very useful as well.

But, please, could you take a look at that part of the code to check if there was a bug for that function?

Thanks

Hi @fxDreema

It looks like that the issue is also reproducible with the "Modify Variables" block with the Variables pane

Thanks

Hello @fxDreema

I have got some compilation error when I fill in some fields on the Variables pane attached to the blocks

When I open up the project with Metaeditor and I compile it, I see which is the problem

What belongs to this block

So, V20 = V19 and V15 = V14 when the block is true. It works as expects for the rest of the variables.

If I use a "Modify Variables" block to shift the valu of those variables, the project compiles without issues.

I can't say that this defect is specifically of the "Counter: Pass once" block because I saw it for other kind of blocks but I am not sure for which ones.

Please, could you be so kind to take a look at the issue?

Thanks

This might be a starting point

Each time P/L is below LossPips, LossPips will be updated to the new value.

Hi @Zackry

As you mentioned, what I suggested works so I guess the variable "los" should be a negative value.

Could you confirm that?

If it is a negative value, I would say that you can´t set a negative value as a Take Profit. It does not make sense. But, if this is the case (trying to set a negative value for TP), you just need to convert the negative value into positive. You can do it by using:

• a MQL code block with MathAbs function

• the adjust field with "*(-1)" [without quotes] in the Take Profit pane on the Sell/Buy blocks

• storing the pips lost directly in positive

....

Not tested

A distance between two levels comes in points or "pips as a price fraction".

This could be an approach

Storage the distance in a variable -> dist_points = (Upper Level - Lower Level)
Convert to pips -> dist_pips = (dist_points / pointsize)

Example:

EURUSD, (pointsize customized) = 0.0001

dist_points = (1.25651 - 1.25632) = 0.00019 points
dist_pips = (0.00019 / 0.0001) = 1.9 pips

You can get the PointSize of the forex pair in the Market Properties menu