"Holder" parameters about qcodes HOT 3 CLOSED

@AdriaanRol I would say there are only 2 types of parameters: ones that you measure (such as temperature), and ones that you get/set occasionally (such as a sweep rate).
IMHO the software parameter, holder and simple/basic parameter all fall into the first category, which would just be covered by add_parameter, which could be a property. If you want the parameter to do something specific, you specify that by passing an fget or fset function that either 1) updates a software attribute, 2) updates an instrument attribute or 3) acts as a 'holder'. Whenever a parameter is changed, this is logged. This way, we don't make the concept of a parameter too complicated. Do you agree?

from qcodes.

personally I would be in favor of subclassing the Parameter class.
This new class could be in the parameter.py file.
Such a new class is also how I solved the Alazar related problems. A good name has then to be thought of for this new class,
maybe
StorageParameter
InternalParameter
TrivialParameter
etc

from qcodes.

closed by #39 (but feel free to make a new issue if anything comes up when any of you start using it)

from qcodes.