Respuesta

MC Randomize history data by TICK

2 respuestas

huangwh88

Customer, bbp_participant, community, 113 replies.

Visitar el perfil

hace 3 meses #285348

There are two recently added MC retest modes, “Randomize history data (by tick)” and “Modified randomize history data (by tick).”

For backtest precision, we can only select STO or 1 min simulation. What does each tick signify in this case?

0

tomas262

Administrador, sq-ultimate, 2 respuestas.

Visitar el perfil

hace 2 meses #285492

Hola,

you can additional “tick” precision once the main data used for backtesting is tick data (not 1-minute)

0

huangwh88

Customer, bbp_participant, community, 113 replies.

Visitar el perfil

hace 2 meses #285493

Hi, you can additional “tick” precision once the main data used for backtesting is tick data (not 1-minute)

Hola,

you can additional “tick” precision once the main data used for backtesting is tick data (not 1-minute)

Thank you Tomas, I see it now. Another question though: The Java snippet (MC Max change as a % of tick price changes) says ‘This option is supposed to work best with Selected Timeframe precision’.

Is this done to reduce computation time, or was the MC test specifically designed for STO precision?

0

Viendo 2 respuestas - de la 1 a la 2 (de un total de 2)