in_port changes

[smiddy]

in_port as input variable. Would be nice to have it as variable for initialization. What do you think?

[benpruitt]

This definitely makes sense for initialization -- although I think we should either go with a variable name that makes it clear that it's just the in_port for initialization (init_in_port?).

Alternatively, we could modify the API such that the behavior for in_port is the same as the behavior for out_port. For example:

extractToWaste(self, in_port, volume_ul, out_port=None,
                          speed_code=None, minimal_reset=False, flush=False)

would become

extractToWaste(self, volume_ul, in_port=None, out_port=None,
                          speed_code=None, minimal_reset=False, flush=False)

... and in_port would default to self.in_port in the same way that out_port defaults to self.waste_port

Thoughts?

[smiddy]

From my point of view the second option is preferred.

We would save to introduce an additional variable and during the running it is clear which is the in_port by definition of self.in_port.