SciML / SciML/ModelingToolkitStandardLibrary.jl

It would be nice to have `ModelingToolkitStandardLibrary.Blocks.RealOutput()` with variable `y` instead of `u`. Can we?

Open
#441 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
Julia
Stars
171
Forks
49
Avg merge
15h 50m
Merged PRs (30d)
10

Description

In the library inside the module Blocks, we have RealInput() and RealOutput() causal models. Both have variables u. However, at least in control literature here in the Nordics, I have seen using u for input and y for output. It would be nice to have RealOutput() with variable y. Can we? `

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the Blocks module by locating the definitions of RealInput() and RealOutput(), then inspect how the output variable is referenced elsewhere. Compare the requested y naming with existing usages and determine whether compatibility implications need to be addressed. Done means RealOutput() exposes the requested output variable without breaking the library's existing model behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
julia
Domain
backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.