Overwriting parameters in inherited instruments about qcodes HOT 12 CLOSED

Three options come to mind:

1. already possible: call del self.parameters['snazzy'] before self.add_parameter('snazzy', ...)
2. we could add a keyword to add_parameter that enables overwriting
3. to avoid even creating such parameters in the first place... this is a little hacky, but you could call super().__init__ after the new params with a pattern like:

def __init__(self, ...):
    # first add the overridden parameters
    self.add_parameter('override1', ...)
    self.add_parameter('override2', ...)
    ...

    # tell add_parameter() to not raise on overrides, just return without adding
    self.ignore_override_errors = True
    super().__init__(...)
    # turn off this behavior afterward
    self.ignore_override_errors = False

we could even get fancy and make this a context manager so you can't forget to clean up:

with self.ignore_override_errors:
    super().__init__(...)

from qcodes.

@alexcjohnson
I like "the with self.ignore_override_errors" option, however I would make it a private function.

from qcodes.

@AdriaanRol can you provide some examples where you would want to do this ?

from qcodes.

@giulioungaretti you could have a base awesomeness instrument, and have special drivers for models or versions that have a slightly different commandset or extended functionality or something like that.

from qcodes.

@MerlinSmiles fair point !

from qcodes.

So the proposed solution is to have an explicit overwrite_parameter function.
@AdriaanRol and @MerlinSmiles what you think ?

from qcodes.

@giulioungaretti would it break anything to be able to overwrite existing ones by default?
One might of course break something by doing so...

from qcodes.

I would propose as an argument in add_parameter, not a special function.
The current trick @alexcjohnson proposed based on del self.parameters['parameter_name'] does the trick but it is hard to gaurantee that all traces get removed if we at a later stage decide to change the functionality.

from qcodes.

I think it make more sense be explicit and avoid confusion. In this way you
will be warned both if you overwrite when adding and vice versa.
On Wed, 1 Jun 2016 at 14:19, MerlinSmiles [email protected] wrote:

@giulioungaretti https://github.com/giulioungaretti would it break
anything to be able to overwrite existing ones bu default?
One might of course break something by doing so...

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
qdev-dk-archive#32 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/ACkcNzOExni8ynUAWYIXnkegF_9aCBIrks5qHXi_gaJpZM4HZLTb
.

from qcodes.

@AdriaanRol not sure what you mean with traces.
It's in general harder to reason about parameters (especially if they have default values, as it would be in this case) when refactoring.

from qcodes.

@AdriaanRol how about implementing as you proposed an add_praemter(...., overwrite=False) ?

from qcodes.

This is now possible via #3125

from qcodes.