It seems you are using the genetic algorithm for optimization. In this case passes will be different even between subsequent optimization on the same machine.
Best regards,
Panagiotis
Yes it’s genetic , is grid more precise ?
Yes but it will take much more time to complete. It's a compromise between speed and accuracy
Please share the code you are using to print these values.
Best regards,
Panagiotis
Hi - see code below. Thanks.
protected override void OnStart() { _macd = Indicators.MacdCrossOver(SlowMAPeriod, FastMAPeriod, SignalLinePeriod); Print("MACD-Analysis started with MACD parameters: Fast MA = {0}, Slow MA = {1}, Signal Line = {2}", FastMAPeriod, SlowMAPeriod, SignalLinePeriod); }
// Check for zero-line crossing if (lastMACD.HasValue) { if ((lastMACD < 0 && macdValue > 0) || (lastMACD > 0 && macdValue < 0)) { // A zero-line crossing occurred ProcessWave(macdValue < 0); } }
lastMACD = macdValue; // Update the last MACD value //Print("Last MACD = " + lastMACD) ;
}
Hi there,
You are printing the _macd.MACD.LastValue which prints the value of the current at the opening of the bar and then you compare it with the MA values of closed bars. The LastValue can change by the time the bar is closed. You should print _macd.MACD.Last(1) instead.
Best regards,
Panagiotis
I have checked the same piece of code in the “Calculate” event when drawing the Indicator and used it in various "On" events of a cBot and they do not perform equivalently, at least not in my calculations. Hence, the same piece of code will fire at different times and produce different results.
I have tried to perform the same calculation in OnTick, OnBar and OnBarClosed and NONE of them yield the same values that are correctly being produced in the “Calculate” event for an Indicator.
Can you guide please?
Hi there,
I have explained to you what the issue is in my previous reply. I am not sure what other guidance you need. If you still use the same piece of code, you will experience the same problem.
How about use your own historical data to emulate this factor ?
Hello and thanks for your reply. Unfortunately I don't have data other than those provided by the Ctrader charts. In case I manage to get other data, could you please explain what you mean by “emulate this factor”? Furthermore, do you know if Spotware has plans to fix this issue? Could someone from Spotware please comment here?
Thanks and best regards, Stefan
Hi there,
This is not supported at the moment and will not be supported in the future as historical data regarding market hours are not available.
It seems you are using the genetic algorithm for optimization. In this case passes will be different even between subsequent optimization on the same machine.
It seems you are using the genetic algorithm for optimization. In this case passes will be different even between subsequent optimization on the same machine.
There is no built in feature for this. You would need to write your own custom functionality to export all this information in a format of your choice.
Where exactly do you want to see this information? In the log?
Best regards,
Panagiotis
Hi,
I would like to view this after optimization in the events tab. But with that said, I don't know if this is even an option do.
Currently it displays 4 event types,
Create Position
Take Profit Hit
Stop Loss Hit
And the one related to the MA Exit criteria displays as: 4. Position Closed
But in doing so, does not tell me which MA Type was actually triggered.
Please let me know if this is possible or if there is a way you would recommend so I can see which MA's perform the best in use of an exit criteria so I can eliminate one's that underperform and keep the one's that do and re-run the optimization accordingly.
Thank you!
Hi there,
You can't modify what is written in the Events tab. You can only print information in the Log. Ideally you should use it to print the information that is meaningful to you.
PanagiotisCharalampous
30 Dec 2024, 08:11
Hi there,
You should be able to choose which columns you can see by right clicking in the grid's header.
Best regards,
Panagiotis
@PanagiotisCharalampous