-
### Background
Trackmate provides a rich set of UIs for users to modify the results from automatic algorithms. For example, it has keyboard shortcuts to either delete or add new spots. However, if …
-
We can already convert a code or a parity check tableau into a faults matrix or a tanner graph. But generalizations of the tanner graph to things like stim/pymatching's "detector error model" would be…
-
```
Compiler annotations such as acquired_before and acquired_after under
-Wthread-safety in clang give information on expected lock order, but they
aren't enforced in runtime.
We could enforce thi…
-
```
Compiler annotations such as acquired_before and acquired_after under
-Wthread-safety in clang give information on expected lock order, but they
aren't enforced in runtime.
We could enforce thi…
-
```
Compiler annotations such as acquired_before and acquired_after under
-Wthread-safety in clang give information on expected lock order, but they
aren't enforced in runtime.
We could enforce thi…
-
```
Compiler annotations such as acquired_before and acquired_after under
-Wthread-safety in clang give information on expected lock order, but they
aren't enforced in runtime.
We could enforce thi…
-
```
Compiler annotations such as acquired_before and acquired_after under
-Wthread-safety in clang give information on expected lock order, but they
aren't enforced in runtime.
We could enforce thi…
-
```
Compiler annotations such as acquired_before and acquired_after under
-Wthread-safety in clang give information on expected lock order, but they
aren't enforced in runtime.
We could enforce thi…
-
```
Compiler annotations such as acquired_before and acquired_after under
-Wthread-safety in clang give information on expected lock order, but they
aren't enforced in runtime.
We could enforce thi…
-
```
Compiler annotations such as acquired_before and acquired_after under
-Wthread-safety in clang give information on expected lock order, but they
aren't enforced in runtime.
We could enforce thi…