AWS Quantum Technologies Blog
Tag: OpenQASM
AWS open-sources OQpy to make it easier to write quantum programs in OpenQASM 3
In September 2021, we announced that AWS would be joining the OpenQASM 3 Technical Steering Committee in an effort to establish a consistent, industry-wide approach for describing quantum programs. In that blog post we also shared our plans to help extend the OpenQASM ecosystem to work with hardware being developed at the AWS Center for Quantum Computing. […]
Amazon Braket launches Braket Pulse to develop quantum programs at the pulse level
When experimenting on a quantum computer, customers often need to program at the lower-level language of the device. Today, we are launching Braket Pulse, a feature that provides pulse-level access to quantum processing units (QPUs) from two hardware providers on Amazon Braket, Rigetti Computing and Oxford Quantum Circuits (OQC). In this blog, we present an […]
Applying classical benchmarking methodologies to create a principled quantum benchmark suite
In this post, we will discuss the current landscape of quantum benchmarking and introduce SupermarQ, Super.tech’s suite of application-based benchmarks designed to overcome the limitations of existing approaches. SupermarQ uses Amazon Braket for device-agnostic access to gate-based quantum processing units (QPUs), so benchmarks can highlight the heterogeneity of quantum computers and their various strengths in […]
Amazon Braket launches OpenQASM support
Last year, we announced that AWS had joined the OpenQASM Technical Steering Committee to help shape a unified approach to express quantum programs across a variety of different hardware technologies. Today, we are excited to announce that customers can now run OpenQASM programs on all gate-based devices on Amazon Braket. Quantum computing is a nascent […]
AWS joins the OpenQASM 3.0 Technical Steering Committee
In the early 1990s, James Gosling introduced the Java programming language. One of the key advantages to Java was that programmers could write code once and have it run on many different backends, without needing to concern themselves with the underlying hardware. This was enabled by an intermediate representation called Java bytecode. Java programs were […]