Lemonergy · Studio block

Physical signal step

A typed physical signal that changes once at an authored time.

Implementation ID
signal-step
Reviewed
2026-10-27

Behavior

The output equals before for t < atS and after from t = atS. Declare the signal quantity to match the receiving port; dimensionless is the default.

Interface

Physical signal step interfaceInputs or arguments on the left, observed outputs on the right. Conserving terminals appear below the component. The tables give units and behavior.Physical signal stepStudio blockout
Original Lemonergy interface view. Lines identify ports; they are not a completed simulation circuit.
Ports and observed outputs
NameDirectionUnitMeaning
outoutputdeclared signal quantityObserved result from the solved component or sampled controller.

Parameters

Defaults are initial model values. Select values for your own model and operating conditions.

Configuration fields
ParameterUnitDefaultMeaning and limits
Before
before
declared signal0Configured model parameter; the default is an initial editor value, not an operating recommendation.
Minimum -1000000000000; Maximum 1000000000000
After
after
declared signal1Configured model parameter; the default is an initial editor value, not an operating recommendation.
Minimum -1000000000000; Maximum 1000000000000
At S
atS
s1Configured model parameter; the default is an initial editor value, not an operating recommendation.
Minimum 0; Maximum 1000000000

Equations and rules

  • out(t) = before for t < atS; after otherwise

Worked example

Supply an outage load

An ideal 10 kWh usable budget supplies 3 kW for 3.33 h before losses and limits.

Open the Studio example →

Use in a workflow

Supply an outage load

V2H illustrates outage-triggered dispatch and reserve.

  1. Physical signal step: Asserts outage
    • before / after
    • atS
Open the Studio example

Connected concepts

Limits and interpretation

Implementation sources

This reference follows Lemonergy implementation sources. Scientific articles support the linked concepts separately.

Repository: battery-design · Revision: ef9802329b75bc15bb96885f8ed5d49425106696

  • js/charging-control.js
  • js/charging-scenarios.js
  • docs/CHARGING_BLOCKS_SPEC.md
  • js/physical-network.js

This implementation and its workflow uses (JSON) · Knowledge graph (JSON-LD)