SciML / SciML/ModelingToolkitStandardLibrary.jl
Mux/Demux missing
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 171
- Forks
- 49
- Avg merge
- 15h 50m
- Merged PRs (30d)
- 10
Description
A component that has a connector RealInput(2) can not be interfaced with two separate signals like
connect(input1, signal1)
connect(input2, signal2)
since the input connector is vector valued. For this, a Mux block would be required
connect(signal1, mux.input1)
connect(signal2, mux.input2)
connect(input, mux.output)
Having said that, I find Mux/Demux very awkward and wouldn't mind a more elegant solution to this problem.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named in the issue. Start by tracing how vector-valued RealInput(2) connectors and connect calls are implemented, then determine whether Mux/Demux or a more elegant interface is appropriate. Done means two separate signals can be connected to the vector input and the proposed interface is covered by an example or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100