Home Progress report - November 11: Checkpoint #2
Post
Cancel

Progress report - November 11: Checkpoint #2

Summary since October 7 Checkpoint #1

Progress Summary

The version 1 of the implementation showcased on October 7 - Checkpoint #1 now has several fixes and changes with regards to the translator functionality with conformance to the OpenQASM 3.0 specification. Here are a few changes summarized on the v1 implementation:

  • Type system flaws identified and fixed in conformance to specification
  • Implementations for quantum and classical registers now robust in aliasing.
  • Initial implementation of ‘duration’ as per specification
  • Cleanup and reconciling minor changes that further strengthen stricter conformance to implementation according to specification.

Contribution Summary:

  • PR #295 : Suggestion to add Scope for power operator for complex types in language specification. Discussions taken up at TSC meeting. Discussions of requirement of dot notation of complex numbers for few rare use case implementations.
  • Issue #296 : Following discussion with @taalexander at IEEE Quantum Week on OpenPulse grammar implementation and Jacks further discussions, team is now added to the openpulse closed group for discussion with guidance from people and teams working on OpenPulse.
  • PR #269 : PR merged this month. Team contributed to bug and implementation fixes for merged reference AST implementation.
  • Issue #304 : Bug report for openqasm3 pyPI package.
  • Presented progress and project overview at Qiskit advocate session at IEEE Quantum Week 2021.

Goals and further direction:

  • Reconstruct and restart current repository to depend on openqasm package rather than forks of openqasm repository and outsource package dependencies for openasm parser, ast and other components
  • Work in support of PR #295 and fulfillment of Issue #296.
  • Take inspirations from discussions in Issue #296 and start writing to invent own grammar and connect it to openpulse, eventually towards an implementation for translating to qiskit-pulse/ qiskit-pulse builder syntax.
  • Take opinions and hints from openpulse invested parties in the discussion in Issue #296 while creating it along. Have received guidance support from openpulse closed group

Checkpoint #2 Document

This post is licensed under CC BY 4.0 by the author.