OpenQASM Export Compatibility
AutomationGlance exports a gate subset of OpenQASM 2.0; it does not import OpenQASM.
What is supported
The simulator's Copy QASM action translates current DSL in the browser. Modeler artifacts are exported by the API. Both emit OPENQASM 2.0;, include "qelib1.inc";, a q register, and a c register when measurements exist. The public DSL gate set maps to h, x, y, z, s, t, rx, ry, rz, u3, cx and cz; CNOT becomes cx. Numeric angles are radians. Unsupported gates cause an export error.
This is export only, not an OpenQASM interpreter or importer. OpenQASM 3, custom gates, classical conditions, reset, loops, opaque operations, hardware mapping and noise instructions are not supported. Exporting a circuit does not execute it in another SDK or on a QPU.
Measurement and ordering
All unitary gates precede exported measurements, matching DSL terminal sampling. Measurement statement number k maps its selected q[i] to c[k]. Comments record the mapping. AutomationGlance displays measured bits in statement order, while tools may display the classical register in reverse order. Use the bit-order example before comparing results.
Example export
OPENQASM 2.0;
include "qelib1.inc";
qreg q[2];
creg c[2];
h q[0];
cx q[0],q[1];
measure q[0] -> c[0];
measure q[1] -> c[1];Equivalent to the Bell example in the DSL reference; exporter output also includes order comments. For best cross-export consistency, use one initial declaration, finite numeric angles, distinct two-qubit operands and no empty comma arguments. Export syntax validation is not a claim of tested SDK/hardware interoperability.