Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Calculation tree visualization labels parameters as attributes

Aperta
  • Qualcosa non va?
#1,576 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go, jupyter
Ambito
backend

Direzione di ricerca

Start by reading the Go code that handles the Jupyter kernel’s %viz command and renders calculation trees; the issue does not name specific files or tests. Reproduce the supplied A::add example and compare its rendered nodes with the described calculation notation. Done means x and y are identified as input parameters and the result is distinguished as the result parameter.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

spec compliance

What happened, and what I expected instead

The Jupyter kernel's default tree visualization does not clearly render calculation parameters. For the calculation below, OpenSysML shows x and y as «attribute» nodes and renders the result as an unlabeled attribute node. The parameter direction and the result role are lost in the visualization.

This report concerns visualization only; it does not claim that parsing or calculation semantics are incorrect.

Reproduction

In a SysML Jupyter kernel, execute:

package A {
    private import ScalarValues::*;
    calc add {
        in x : Integer;
        in y : Integer;
        return : Integer;
        x + y
    }
}

Then render the calculation with the OpenSysML visualization command (for example, %viz A::add).

OpenSysML's output represents x and y as «attribute» and the result as a generic attribute node.

Image

Comparison with the OMG Pilot

Running the same model and %viz A::add in the OMG SysML v2 Pilot produces a calculation box labeled «calculation» add, with x and y shown as input ports and result shown as an output port. This makes the calculation's parameters and result explicit. The pilot output is comparative implementation evidence, not the authority for the standard.

Image

SysML graphical-notation reference

Compared against SysML 2.0, release 2026-08:

  • Section 7.19.2, Calculation Definitions and Usages (pp. 156–157) explains that directed usages declared in a calculation body are parameters and that a calculation has a result parameter.
  • Section 8.2.3.19, Calculations Graphical Notation (pp. 269–271) describes a calculation usage node with parameter positions (param-t*, param-l*, param-r*, param-b*), an action-flow view, and compartments including the result compartment.
Image

These graphical-notation clauses are informative, so this is reported as a rendering discrepancy against the standard's described notation, not as a violation of a normative requirement. The rendered nodes should identify calculation inputs/results as parameters rather than generic attributes, and distinguish the result from other parameters.

This is a separate calculation-rendering case from #1532, which reports other tree visualization discrepancies.

Lingua principale
Go
Stelle
47
Fork
13
Merge medio
15h 52m
PR unite (30g)
906

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Open-MBEE/OpenSysML

Tutte le issue di Open-MBEE/OpenSysML

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.