Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exchange frequency Keyword by period (or something better) #21

Open
BoergeSt opened this issue Jul 8, 2022 · 2 comments
Open

Exchange frequency Keyword by period (or something better) #21

BoergeSt opened this issue Jul 8, 2022 · 2 comments
Labels
bug Something isn't working good first issue Good for newcomers
Milestone

Comments

@BoergeSt
Copy link
Member

BoergeSt commented Jul 8, 2022

Using frequency for the time between function calls is kind of confusing, since frequency is usually given in 1/s and not in seconds. => We should exchange this by something more descriptive. I propose period, however, as I am not a native English speaker, I am open to suggestions.

@BoergeSt BoergeSt added bug Something isn't working good first issue Good for newcomers labels Jul 8, 2022
@BoergeSt BoergeSt added this to the Release v1.1 milestone Jul 8, 2022
@lodenrogue
Copy link

Period could work or you could go with

duration
time_span
run_time
delay
lag_time
latency

@BoergeSt
Copy link
Member Author

First of all, thanks for your suggestions.
I personally feel like "duration", "time_span" and "run_time" indicate some form of time passed for the process rather then between two consecutive function calls.
Under "lag_time" and "latency" I would probably understand the time between the scheduling and the actual execution of a function. The same goes for delay, and I already used it for this purpose for 'delayed' Connection Executions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants