range(-9,8) min value was converted to a uint32 in lascar, which made it try to allocate a 16GB buffer. Avoid this problem by providing a positive range by offsetting the observed difference
Numba complains about not being able to convert a char like "1" into an int, so perform this conversion explicitly
Remove HW preprocessing of traces as now the default tracer does it already
range(-9,8)min value was converted to auint32in lascar, which made it try to allocate a 16GB buffer. Avoid this problem by providing a positive range by offsetting the observed difference