Skip to content

Output inconsistent with Quipper ASCII #1

@eddieschoute

Description

@eddieschoute

While trying parsing these output files there were a few errors in the output format that do not follow the ASCII format as output by Quipper. I am not using Quipper itself to parse these files but rather parsing them using my own parser based off Quipper's Printing.hs.

  • Some files have the circuit input and output arity specified strangely where there is an extra comma after the last qubit, e.g. the files gf2^E163_mult_after_light and gf2^E64_mult_after_light.
  • There are also some files that have more than one newlines at the end. E.g. pf6_30_before.
  • Most gates have "no control" appended to them even though they have a control. This seems like default Quipper behavior though? But from correspondence with @njross it seems unintended.

Now of course this is being fairly nitpicky, but it does necessitate releasing more constraints on the parser to be able to parse your output files correctly. These weird outputs would otherwise give me errors when parsing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions