There is totally no way of loading data-logger style time&value tables.
The current version 5 is still unable to interpret time columns from csv, or other tables by any means.
The situation is absurd and fatal. It is the most common way of saving physical sensor/probe data (either from hardware, or simulation). And neither binary sources, nor numpy scripting allow for importing every data row as a separate timestep. Meanwhile, ParaView itself allows assigning exact time to every timestep. The "ProgrammableSource" have no methods for reading correctly all the float-time timesteps.
(!)Moreover, when loading integer timesteps (i.e. 1s, 2s, 3s etc) ProgrammableSource can be used only once per session. The next time you try executing, or recreating it, there are random errors, like "no global value", while the same code works after ParaView restart.
I kindly ask adding a new feature to the roadmap:
- A table source filter with a column assignable as time.
Modyfying the current table source with a feature of assigning a time-column would work just well.