Sets ticksize and tickvalue

[kenorb]

when tickstory generates FXTs, it write additional info into fxt, like ticksize tickvalue, python tool , lack of such info

golang only provide limit parameter when write header in FXT, so when I BT, the tester read the ticksize=0

FXT by tickstory:

Our version:

the golang tool missing some important info also,

So I conclude tickstory is best choise now , if dont have TDS2

tickstory provide an visual tool to check FXT header