# Proposal: add a way to access ParaView's requested time in Python Calculator/Annotation
**URL:** https://discourse.paraview.org/t/proposal-add-a-way-to-access-paraviews-requested-time-in-python-calculator-annotation/16903
**Category:** Development
**Tags:** python, proposal
**Created:** [July 7, 2025, 3:26pm UTC](https://discourse.paraview.org/t/proposal-add-a-way-to-access-paraviews-requested-time-in-python-calculator-annotation/16903 "2025-07-07T15:26:08Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [July 7, 2025, 3:26pm UTC](https://discourse.paraview.org/t/proposal-add-a-way-to-access-paraviews-requested-time-in-python-calculator-annotation/16903/1 "2025-07-07T15:26:09Z")
The **Python Calculator** and **Python Annotation** filter let you refer to the current time and time index of the source they are connected to via the `t_value` and `t_index` variables and the `{timevalue}` and `{timeindex}` string substitutions. This is great if you want to use the time values associated with the data source.
However, there are use cases where you might want to use ParaView’s requested time instead. This is not currently possible to access in **Python Calculator** or **Python Annotation** , but I think it would be nice to be able to do that. For example, if you want to compute a time-varying function over a static dataset (a dataset that has one timestep) for animation purposes, it would be nice to get ParaView’s requested time as managed by the Time Manager rather than be stuck at the single non-varying time value associated with the static dataset.
I propose adding to **Python Calculator/Annotation** ;
- `t_time` as a local variable
- `{time}` as a string replacement
or maybe
- `t_requestedtime` as a local variable
- `{requestedtime}` as a string replacement
These are my first thoughts for names and can likely be improved. I want to stay away from “t\_paraviewtime” because ParaView-derived applications may make use of this feature, but won’t be called ParaView.
---
### Author:  [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [July 7, 2025, 4:07pm UTC](https://discourse.paraview.org/t/proposal-add-a-way-to-access-paraviews-requested-time-in-python-calculator-annotation/16903/2 "2025-07-07T16:07:54Z")
Sounds good.
If there is more than one time (requested time, dataset timestep time), I would rather the variable be longer and clear. t\_requestedtime seems appropriate to me.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [July 8, 2025, 9:41am UTC](https://discourse.paraview.org/t/proposal-add-a-way-to-access-paraviews-requested-time-in-python-calculator-annotation/16903/3 "2025-07-08T09:41:33Z")
> [@wascott](#):
>
> I would rather the variable be longer and clear. t\_requestedtime seems appropriate to me.
Agreed.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [July 20, 2025, 3:08pm UTC](https://discourse.paraview.org/t/proposal-add-a-way-to-access-paraviews-requested-time-in-python-calculator-annotation/16903/4 "2025-07-20T15:08:24Z")
Thinking more about names, I think `pipeline_time` is a better name.
GitLab issue for this proposal: [https://gitlab.kitware.com/paraview/paraview/-/issues/23025](https://gitlab.kitware.com/paraview/paraview/-/issues/23025)
---
### Author:  [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [July 21, 2025, 4:44pm UTC](https://discourse.paraview.org/t/proposal-add-a-way-to-access-paraviews-requested-time-in-python-calculator-annotation/16903/5 "2025-07-21T16:44:49Z")
Perfect.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [July 22, 2025, 2:55pm UTC](https://discourse.paraview.org/t/proposal-add-a-way-to-access-paraviews-requested-time-in-python-calculator-annotation/16903/6 "2025-07-22T14:55:49Z")
I ended up going with `current_time` as the variable name as that matches a Current Time UI element in the Information panel
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [July 22, 2025, 2:56pm UTC](https://discourse.paraview.org/t/proposal-add-a-way-to-access-paraviews-requested-time-in-python-calculator-annotation/16903/7 "2025-07-22T14:56:17Z")
Merge request here: [https://gitlab.kitware.com/paraview/paraview/-/merge\_requests/7403](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/7403)
This will be in ParaView 6.1.