You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Are the recent changes in the Hamiltonian because the set_config() exists and thus the dimensions might change if leakage is added?
Yes indeed :) I think I have covered everything on this side. However, if you feel it's too much trouble for a feature that is not too much used, another option could be to just raise an error when the user do set_config, with a Config having a different leakage than the previous config...
Yes indeed :) I think I have covered everything on this side. However, if you feel it's too much trouble for a feature that is not too much used, another option could be to just raise an error when the user do set_config, with a Config having a different leakage than the previous config...
It's just that I think we'll want to deprecate set_config() so it seemed like hassle, but if you think you have covered everything then there is also no need to revert the changes
Yes indeed :) I think I have covered everything on this side. However, if you feel it's too much trouble for a feature that is not too much used, another option could be to just raise an error when the user do set_config, with a Config having a different leakage than the previous config...
It's just that I think we'll want to deprecate set_config() so it seemed like hassle, but if you think you have covered everything then there is also no need to revert the changes
We obtain the same results as before with the same input
If the collapse operator provided with leakage does not have any term in associated with a projection on "x", then the result is the same as without leakage (and the CoherentResult state have 0 on all the terms associated with the "x" state).
**Main changes:**
- Reworking the NoiseModel interface (#710)
- Allow modification of the EOM setpoint without disabling EOM mode (#708)
- Enable definition of effective noise operators in all basis (#716)
- Add leakage (#720)
- Support differentiability through Torch tensors (#703)
- Add from_abstract_repr to Device and VirtualDevice (#727)
- [FEAT] Handle batches with partial results (#707)
- Add open batches to pulser-pasqal (#701)
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.
Implements the "leakage" noise. When "leakage" is provided as a
noisein theSimConfig:operatorsin Hamiltonian (seeconstruct_hamiltonian) since they changed size