Assign time to a timestep

Is there a simple way to assign time to a timestep without going to python?
I have a field data step-by-step evolution loaded as enumerated file series.
So in Paraview it appears as time 1,2,3,4,5…
But I know the exact time vector, with a value for every time step.
I also know the uniform time difference for every step. like dt=1.2494e-09.

It is possible assigning this difference to the time data? Like scaling the time vector 1.2494e-09:1 ?
I need it for further taking FFT and checking spectrum at particular spatial positions.

You can specify it in a .pvd file.

I can’t if it is not provided.
The step-by-step data is old-format vtk. so there are only steps available. The step time difference is something I calculate separately.

The question is not about loading, but about assigning correct time to the data already loaded with integer time.

There is no such Filter in ParaView yet, and it actually is not a trivial feature to add because of the way timesteps works in VTK.

Why is it not trivial? In the timestep properties I can type in any float number for any timestep iterator manually. Why can’t it be just filled in on incremental basis with a filter? or overwritten by a vector of values using another filter?

time steps have to be provided during the RequestInformation pass. It is not trivial to have access to the timesteps at this point.

How about that:

If you are also the generator of the VTK files, you could add in as FIELD_DATA, which presumably makes it available for you to access in ParaView.
We use the field name TimeValue for compatibility with what Catalyst generates.

If it is just scaling the time you can use the Temporal Shift Scale filter.

Mathieu, oh, you mean it is created during import? And not accessible to filters?
Technically, import sources are also kind of filters…
And you can take data from one source and map it to the grid from another source.
Why can’t we generate a custom timestep source, and map a data with grids to that? But I didn’t find a way for doing it with a few mouseclicks.

Jean that is interesting!
It still needs a lot of scripting, because I am not the source of files, and get the dataset of unknown length form the binary solver.

Temporal Shift Scale filter, it is interesting, but I did not get how it works, so skipped it as not related. Now I will check it again…

the time is scaled, but the data stays out of time scope at 1,2,3,“seconds”, while we are speaking in term of picoseconds… so it is not an applicable filter. I don’t even understand what it does and who would need it…