Refresh remote seeds for executions within a client session #1318
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
bmhowe23
approved these changes
Mar 1, 2024
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Currently, when sending REST requests to a remote QPUD, the seed value is set to
cudaq::get_random_seed(), hence all kernel executions will be using the same seed value. This deviates from the local execution model, whereby the static random number generator in the simulator is seeded once whenset_random_seedis called.This PR fixed that difference by letting the client to seed the server using a random number generator seeded by
cudaqseed value.Note: in general, we don't expect an absolute seed value to have the same effect between local execution and remote execution. Hence, we can randomly generate the server seed using a random sequence seeded by the
cudaqseed.