Melody
Melody
**Application** Even when using templates, there is still duplicate code in `.circleci/config.yml`. For example, ``` version: 2 .. test-osx-3.6:
**Application** It would be nice to have the expected QPU runtime of each demo in the README. In that way, users can make an informed decision on how running the...
**Application** Currently, CircleCI builds and caches a virtual environment for each demo. This is wasteful especially if many of the demos share the same requirements.txt (i.e. they can run in...
**Description** If a previously existing demo gets its name changed, its `old_name/` dir still exists in CircleCI. When the bash in the CircleCI config file gets run, it will check...
**Description** At the moment, the base for the shortest schedule penalty is `number of jobs + 1`. However, in the derivation, the base is total number of TASKS + 1....
**Application** Currently, whenever the code is updated, CircleCI runs all the unit tests available in the demos repo. Since the demos repo has many independent demos and not all demos...
**Application** In qboost, there are two files `demo.py` and `demo.ipynb`. I suspect the initial idea was that the user can learn through the notebook, with the option to run the...
**Application** Heuristic unit tests occasionally fail because they return a suboptimal solution. This is annoying, because the code might be fine.  **Proposed Solution** Make a more reliable unit test....
**Application** Currently, the penalty to encourage the shortest schedule is based on geometric series. This penalty can easily over take the other penalties created by the other constraints. Some thought...