Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Matrix-free Measurement Mitigation (M3).
M3 is a measurement mitigation technique that solves for corrected measurement probabilities using a dimensionality reduction step followed by either direct LU factorization or a preconditioned iterative method that nominally converges in O(1) steps, and can be computed in parallel. For example, M3 can compute corrections on 42 qubit GHZ problems in under two seconds on a quad-core machine (depending on the number of unique bitstrings in the output).
Online Documentation @ Qiskit.org
You can pip
install M3 in using PyPi via:
pip install mthree
This will install an OpenMP optimized version on Linux, and serial versions for OSX and Windows. Alternatively, one can install from source:
pip install .
To enable openmp one must have an openmp 4.0+ enabled compiler and install with:
MTHREE_OPENMP=1 pip install .
On OSX one must install GCC using homebrew:
brew install gcc
Then installation with openmp can be accomplished using a call like:
MTHREE_OPENMP=1 CC=gcc-14 CXX=g++14 python setup.py install
Note that previously the instructions said to install LLVM and NOT GCC. However, in the latest version of OSX (Sequoia) LLVM based installations will build, but segfault upon execution. GCC however works fine, thus the change above.
M3 is simple to use:
import mthree
# Specify a mitigator object targeting a given backend
mit = mthree.M3Mitigation(backend)
# Compute the 1Q calibration matrices for the given qubits and given number of shots
# By default it is over all backend qubits at 10000 shots.
mit.cals_from_system(qubits, shots)
# Apply mitigation to a given dict of raw counts over the specified qubits
m3_quasi = mit.apply_correction(raw_counts, qubits)
Note that here qubits
is a list of which qubits are measured to yield the bits in the output.
For example the list [4,3,1,2,0]
indicates that a measurement on physical qubit 4 was written to
classical bit zero in the output bit-strings, physical qubit 3 maps to classical bit 1, etc.
The fact that the zeroth bit is right-most in the bitstring is handled internally.
It is possible to compute error bounds in a similarly efficient manner. This is not done by default, but rather turned on using:
m3_quasi = mit.apply_correction(raw_counts, qubits, return_mitigation_overhead=True)
Then the distribution itself can be called to return things like the expectation value and the standard deviation:
expval, stddev = quasi.expval_and_stddev()
The results of M3 mitigation are quasi-probabilities that nominally contain small negative values. This is suitable for use in computing corrected expectation values or sampling problems where one is interested in the highest probability bit-string. However, if one needs a true probability distribution then it is possible to convert from quasi-probabilites to the closest true probability distribution in L2-norm using:
closest_probs = m3_quasi.nearest_probability_distribution()
FAQs
M3: Matrix-free measurement mitigation
We found that mthree demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.