Jonas Hörsch
Jonas Hörsch
Tulipa.jl has quite some research on the topic.
The match statement is consistent with the minimal python version 3.10. https://peps.python.org/pep-0636/
@gianvicolux I think if you add a small release note this is ready for review.
> I didn't notices that `at_port` is just this: > > ``` > if not at_port: > ports = [ports[0]] > ``` > > which makes this PR a bug...
> I am happy with: > > > at_port: Literal["all"] | int | Sequence[int] = [0] > > And I agree, `c.ports` is not great. It returns `""` for single...
Hmm .. i thought some more. There will be recurringly the need to accept both types of inputs, `port_cols` and `port_nums`. What about a new dataclass: ```python type PortsLike =...
Not sure what's the difference between internal, external. here. I'd expect the overhead to be negligible. You'll need at least two methods `_as_ports(:PortsLike) -> Sequence[int]` and `_as_port_cols(:PortsLike, :Component) -> Sequence[str]`....
Rebased to the actual master now. Had an old state. The test failures are deprecations in the master branch.
Hi, @euronion, the reference_bus would then be for fixing the units for capital and marginal costs? Efficiencies are already fully determined by the ratios of the rates. Not sure what...
I'll wait for #1349 to land and then rebase on that.