Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Showing alarm limits in data browser

Open
#3,889 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
java

Research direction

Start by reading the RTPlot APIs, especially PlotDataItem, and trace how alarm limits from PVSamples relate to TracePainterImpl. Compare extending the plotting APIs with using a subclass or data-browser-specific painter; the issue leaves this design choice open. Done means the approach is decided and supports displaying alarm limits for a selected raw-request trace without adding clutter.

Written by the indexing model from the issue text.

Description

A user is requesting the option to visualize alarm limits in a data browser plot. Reason is simplicity (easier than switching to Probe), but also to visualize potential changes in the limits.

Further, the option would be added as a checkbox column in the traces tab. To avoid visual clutter, only one trace at a time would be able to be amended with a visualization of alarm limits. Also, since alarm limits are provided only for a raw request, user would need to actively select that first.

Now the RTPlot APIs (e.g. PlotDataItem) are agnostic to the underlying data providers, it's a bit of a challenge to plot alarm limits originating in PVSamples. So question is if these APIs should be extended to accommodate alarm limits as well. To be noted, a PlotDataItem supports stddev, which may not make sense to all types of data.

Alternatively one could maybe consider a subclass of TracePainterImpl or a data browser specific TracePainter.

Thoughts, anyone?

Dominant language
Java
Stars
130
Forks
132
Avg merge
2d 11h
Merged PRs (30d)
23

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No 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.

More from ControlSystemStudio/phoebus

All issues in ControlSystemStudio/phoebus

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.