Repository navigation
Custom metadata changes the database schema (?!?) #898
Description
Steps to reproduce
Rerun the following code 6 times, each iteration with a different word (of the list ['these', 'tags', 'break', 'the', 'database']) substituted for ####
meas = Measurement()
meas.registerParameter(dac.ch1) # register the first independent parameter
meas.registerParameter(dmm.v1, setpoints=(dac.ch1,)) # now register the dependent oone
with meas.run() as datasaver:
datasaver._dataset.add_metadata('####', '####')
for set_v in np.linspace(0, 25, 100):
dac.ch1.set(set_v)
get_v = dmm.v1.get()
datasaver.addResult((dac.ch1, set_v),
(dmm.v1, get_v))
dataid = datasaver.id # convenient to have for plotting
Expected behaviour
Either a field (e.g. called 'metadata') of the table runs gets filled with a json serialization of the custom metadata, or there is an extra table (metadata: tagid | run_id | name | value) which get populated with the custom metadata tags.
Actual behaviour
System
operating system
qcodes branch
feature/dataset
qcodes commit
Activity
[-]Custom metadata changes the database scheme (?!?)[/-][+]Custom metadata changes the database schema (?!?)[/+]Merge #4784