MétaCan
Menu
Back to cohort
Record W1741323436

Integrating SHriMP with the IBM websphere studio workbench

2001· article· en· W1741323436 on OpenAlexaff
Derek Rayside, Marin Litoiu, Margaret‐Anne Storey, Casey Best

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Research
Canadian institutionsUniversity of Victoria
Fundersnot available
KeywordsWorkbenchComputer scienceIBMVisualizationShrimpSoftware engineeringData flow diagramPortingProgramming languageWorld Wide WebDatabaseSoftwareArtificial intelligence
DOInot available

Abstract

fetched live from OpenAlex

This paper provides an experience report for researchers who are interested in integrating their tools with the new IBM WebSphere Studio Workbench. The Workbench (open source at www.eclipse.org) provides an open framework for building integrated development environments. We report on our experience integrating an information visualization tool (called SHriMP Views) with the IBM Workbench. Although SHriMP was originally developed for visualizing programs, it is content independent. We have re-targeted SHriMP for visualizing flow diagrams. Flow diagrams can be hierarchically composed, thus leveraging the key features of SHriMP that allow a user to easily navigate hierarchically composed information spaces. We discuss the di#erences between programs and flow diagrams both in terms of their semantics and in their visual representation. Terminals, which are a first-class entity that mediate between nodes and arcs in flow diagrams, presented the main challenges here. We also report on the main technical challenges we faced, due to the di#erent widgets sets used by SHriMP (Swing/awt) and the Workbench (swt).

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.840
Threshold uncertainty score0.224

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.014
GPT teacher head0.249
Teacher spread0.235 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designObservational
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations11
Published2001
Admission routes1
Has abstractyes

Explore more

Same topicSoftware Engineering ResearchFrench-language works237,207