READ-ONLY

The forum is now a read-only archive.

For bug reports & platform questions → [email protected]

Our community lives on Discord and YouTube — come join us!

MC Randomize history data by TICK

2 replies

huangwh88

Customer, bbp_participant, community, sq-ultimate, 107 replies.

Visit profile

2 years ago #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

Tomas Matejka

Administrator, sq-ultimate, 2 replies.

Visit profile

2 years ago #285492

Hi,

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

0

huangwh88

Customer, bbp_participant, community, sq-ultimate, 107 replies.

Visit profile

2 years ago #285493

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

Hi,

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

Viewing 2 replies - 1 through 2 (of 2 total)