It looks to me like CKConv.rel_positions is calculated as a torch.linspace, with no option to pass real timestamps. But from what I understood from the paper, the architecture should allow arbitrary timestamps across batches. Is this simply a limitation of the implementation? It seems odd to me to exclude this. I thought handling non-uniform timestamps was a key feature of the model.