Adding hash to Custom

[andrea-pasquale]

Closes #1100.

Checklist:

• Reviewers confirm new code works as expected.
• Tests are passing.
• Coverage does not decrease.
• Documentation is updated.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 50.87%. Comparing base (ed8b3cc) to head (5550a10).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1101      +/-   ##
==========================================
+ Coverage   50.84%   50.87%   +0.03%     
==========================================
  Files          63       63              
  Lines        2903     2905       +2     
==========================================
+ Hits         1476     1478       +2     
  Misses       1427     1427              

Flag	Coverage Δ
unittests	50.87% <100.00%> (+0.03%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[stavros11]

Thanks for the fix. I have not tested on hardware but I assume it fixes the issue with QM. I also confirm that the reason hash is used in the driver instead of id is exactly what is written in #1100 (comment).

Not related at all to this PR, but id should still be used in at least two places: 1. when registering acquisition variables, because every measurement has its own acquisition, even when two measurements have the same waveform for probe, 2. when registering sweepers, because each sweeper affects specific pulses, even if there are other pulses in the sequence with the same waveform. In other cases, the driver is using hash internally:

qibolab/src/qibolab/_core/instruments/qm/config/pulses.py

Lines 23 to 25 in ed8b3cc

	def operation(pulse):
	"""Generate operation name in QM ``config`` for the given pulse."""
	return str(hash(pulse))

to map pulses to operations in the QM config, to avoid duplication in uploaded waveforms.