BSchelpe

Add a version attribute to the DetectorDatabase class

1

This should close #575 Two comments about the code: 1. I'm not sure what numbering system to use for the version. It looks more like a version number in the...

The detector database needs to be invalidated for relevant code changes

4

This came out of PR #573. @nelimee : "We need to be able to version the detector database if we want that feature [the transparent use of the detector database]...

Pre-computed Detector database

1

PR #573 implements Option 2 of Issue #509. Option 3 is still to be implemented, ie ship an already populated database along with tqec and modify the existing interface to...

This will close issue #748. It is currently a draft PR, because it still needs more work doing (most obviously the left-right hadamard implementing) and testing. I am pushing it...

Implement spatial hadamard in the fixed_bulk convention

1

This is the remaining subissue in #561. It is expected to require very similar functions to #631, and so the intention is to work on this after #631 is finished.

Implement remaining spatial hadamard code paths in the fixed boundary convention

4

This will close issue #631 (and also issue #384, I believe - I have not checked the temporal hadamard implementations, as far as I know they do not have issues...

Is it possible to write a useful test for DetectorDatabase.version?

1

At the moment, it is up to the coder to realise when their code changes mean that the version number on DetectorDatabase should be increased. Ideally there would be an...