-
Notifications
You must be signed in to change notification settings - Fork 0
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
ERT -> ERD #3
Comments
The ERT is already taken for "expected runtime" (meaning: average runtime as best estimator of its expectation = sum of runtimes divided by number of successes, I have seen it being read as "empirical runtime" too, which would not be wrong either), hence it's not an option to denote the runtime distribution. We would have the choice between ERD (as used in the 2022 paper) or RTD or ERTD, both of which I kinda like better, also because they keep abbreviating runtime as RT. I can't remember why we ended up using ERD. |
We just discussed the issue some more and came up with runtime profile (RTP) or target runtime profiles (TRTP) with a slight bias towards RTP. |
A disadvantage of "runtime distribution": it suggests data drawn uniformly and independently. |
No description provided.
The text was updated successfully, but these errors were encountered: