Julien Hillairet

> In case my 2 cents regarding lower-grade instruments is useful, I've been interfacing with the NanoVNA (based on nanovna.py) for quite a while now without any issues (and have...

> > In case my 2 cents regarding lower-grade instruments is useful, I've been interfacing with the NanoVNA (based on nanovna.py) for quite a while now without any issues (and...

> This is the first time I might participate in someone else's PR on github. How do I do it? Check out cafeclimber's fork and open a PR to the...

> > > This is the first time I might participate in someone else's PR on github. How do I do it? Check out cafeclimber's fork and open a PR...

For info, the [SweepMe!](https://sweep-me.net/) software (ping @afischer-sweepme ) is a measurement software tool which can use [many different kind of devices](https://sweep-me.net/modules_devices). It also uses scikit-rf for manipulating Touchstone files. They...

Thank you @mhuser for having clarified all this. > I think the confusion is because by default the line method creates a line with characteristic impedance of `z0`, but I...

Yes, something like that. But before implementing things, beware that many things in Media are defined like that, like `match`, etc

Nice summary > I think we could enforce the a, b, c and d behaviour by fixing only `Media.line` method like this: We could make `embed` parameter having no more...

For, creating a line of arbitrary impedance, what if we cascade the operations: ``` my_media = MyMedia(physical_parameters and frequency) my_line = my_media.line(d) # z0 is the charact impedance from the...

> do you mean do this internally or expect user to use this method? I would expect users to use this method, as an explicit workflow, which keeps the original...