-
From https://code.kx.com/q4m3/14_Introduction_to_Kdb%2B/#1423-splayed-tables-with-nested-columns :
When you splay a table with compound columns, q creates not one but two files for each compound column. … If you examine these files you will discover that the sharp file contains the binary data of the original list in flattened form and the non-sharp file is a serialized q list of integers representing the lengths of each sublist of the original list.
In this case, I think your column is doubly compounded which creates both a ot# and ot## file. As the other answerer says, you should be able to use get on the “non-sharped” file just fine.