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

Update docs regarding max_execution_time #991

Closed
1 of 3 tasks
kt474 opened this issue Aug 2, 2023 · 2 comments · Fixed by #1059
Closed
1 of 3 tasks

Update docs regarding max_execution_time #991

kt474 opened this issue Aug 2, 2023 · 2 comments · Fixed by #1059
Assignees
Labels
documentation Improvements or additions to documentation priority: high High priority issue (must have for current release)
Milestone

Comments

@kt474
Copy link
Member

kt474 commented Aug 2, 2023

After the updates are live on the server side (estimated to be ready 8/14), max execution time is now just quantum time and that should be reflected in the docs

Quantum time is defined as

the time that the QPU complex is occupied exclusively by a single job
@kt474 kt474 added the documentation Improvements or additions to documentation label Aug 2, 2023
@jyu00
Copy link
Collaborator

jyu00 commented Aug 2, 2023

Except for simulator jobs... since they obviously don't have quantum time lol

@kt474 kt474 added this to the 0.11.4 milestone Aug 6, 2023
@jyu00 jyu00 added the priority: high High priority issue (must have for current release) label Aug 7, 2023
@jyu00
Copy link
Collaborator

jyu00 commented Aug 22, 2023

We should also issue a warning (once) about this change if a user tries to set max_execution_time.

@kt474 kt474 modified the milestones: 0.12.0, 0.12.1 Aug 29, 2023
@kt474 kt474 self-assigned this Sep 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation priority: high High priority issue (must have for current release)
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants