SciML / SciML/ModelingToolkitStandardLibrary.jl

Why don't many (all?) of the standard library blocks create events for discrete changes in behavior?

Open
#432 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 Simulink, most blocks have events (they call them zero crossings) built into them and you can optionally turn them on/off. ModelingToolkit supports various types of events, but it doesn't appear that most of the blocks in the standard library have them implemented? The DeadZone block for example, has discrete changes in behavior that would make it a good candidate to have events. Is there a reason for not including events at the component level for blocks/components that have logical/discrete changes in their behavior?

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 by reviewing the standard-library components, especially the DeadZone block, and how ModelingToolkit represents events and discrete changes in behavior. Determine whether component-level events should be added and define which blocks and behavior changes are in scope; the issue does not name files or tests, so completion criteria remain to be established.

Written by the indexing model from the issue text.

Assessment

Tech stack
julia
Domain
backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.