Skip to content

Make consistent use of the name for the hardware configuration

Spawned from: !135 (comment 642029883)

Throughout the code base we have several places (e.g. the qblox backend or quantify_scheduler.compilation) where we refer to the "hardware_mapping". Though it is my understanding that in !161 (merged) we formally decided to name this "hardware_configuration". This name should be updated where applicable.