MétaCan
Menu
Back to cohort
Record W2006552151 · doi:10.1109/vissof.2007.4290705

Visualization Patterns: A Context-Sensitive Tool to Evaluate Visualization Techniques

2007· article· en· W2006552151 on OpenAlexafffund
Harkirat Padda, Ahmed Seffah, Sudhir P. Mudur

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Research
Canadian institutionsConcordia University
FundersNatural Sciences and Engineering Research Council of CanadaConcordia University
KeywordsVisualizationComputer scienceContext (archaeology)Software visualizationData visualizationSoftwareInformation visualizationHuman–computer interactionVisual analyticsCreative visualizationRepresentation (politics)Data scienceData miningSoftware systemProgramming languageComponent-based software engineering

Abstract

fetched live from OpenAlex

In the myriad of visualization tools/techniques available to the users, it is hard to fathom the applicability of a given tool/technique to the visualization problem in hand. The tool users/evaluators have no guidance mechanism that could describe the suitability of visualization tools/techniques to fulfill their objectives. A tool may be good in one context and bad in another. This 'context of use' has become a pandemic in almost all measures of evaluations. To deal with this complex factor of tool selection/evaluation, we propose to describe a visualization tool/technique by encapsulating a technique in a pattern format describing the applicable context of use for it. We highlight the usefulness of such visualization patterns for evaluation by describing an exemplar visualization pattern solving a problem of displaying dependencies among software objects in the context of static software structure representation.

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 machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.017
metaresearch head score (Gemma)0.098
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.017
Threshold uncertainty score0.092

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0170.098
Meta-epidemiology (narrow)0.0030.001
Meta-epidemiology (broad)0.0020.001
Bibliometrics0.0110.005
Science and technology studies0.0010.001
Scholarly communication0.0050.008
Open science0.0020.004
Research integrity0.0030.002
Insufficient payload (model declined to judge)0.0070.002

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.025
GPT teacher head0.355
Teacher spread0.330 · 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 source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designBench or experimental
Domainnot available
GenreMethods

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

Citations7
Published2007
Admission routes2
Has abstractyes

Explore more

Same topicSoftware Engineering ResearchFrench-language works237,207