Reason for fidelity equivalence in entanglement generation

[ghost]

Hello,

I am wondering why the assertion here

SeQUeNCe/src/entanglement_management/generation.py

Line 142 in 8cbcbd3

assert self.fidelity == other.fidelity

was added. Can you explain, @xwu64, the purpose of ensuring fidelity equivalence here?

[xwu64]

I don't think it's necessary if the generation is implemented on the real testbed. At here, we are not clear what will the fidelity of entanglement from the generation protocol. Therefore, we just assume both sides of protocols have a consensus of the fidelity of entanglement after the generation protocol. To avoid inconsistency of fidelity of entangled memories, we add this assertion.

Please let us know if you have ideas about this implementation.

[ghost]

Gotcha, thanks!