Login Page - Create Account

Support Board


Date/Time: Sat, 11 May 2024 08:22:27 +0000



Post From: ACSIL sc.TickSize Returns 0*

[2024-03-29 03:41:10]
Gradient - Posts: 41
After removing the studies and restarting the platform, I'm still experiencing the same issue.

CPU exceptions can be caused by division by zero.

In the original study I am dividing by the sc.TickSize which is sometimes zero as I've shown above. This is likely why there is a CPU exception, but it doesn't explain why the sc.TickSize is correct sometimes and zero other times.