Skip to content
#small language model Dataset Open access

User study result and dataset

Sep 2026 · Zenodo (CERN European Organization for Nuclear Research)

Abstract

This record contains the human annotation study underpinning the MSc thesis"Exploring Semantic Consistency in Image Super-Resolution" (Master in ComputerVision, Universitat Autònoma de Barcelona / Computer Vision Center). Super-resolution is normally evaluated on fidelity and perceptual quality — howclose an output is to its reference, and how natural it looks. Neither questionasks whether the reconstruction still means the same thing. A generative modelcan invent a plausible face, produce readable text where the reference had onlya smudge, or turn one object into another, and score well on both axes whiledoing it. This dataset was collected to study that failure mode directly, byasking people what actually changed. It contains 104 super-resolution image pairs and 4,700 annotation records from41 participants, and it is self-contained: every statistic reported in thethesis can be recomputed from these files alone. THE TASK Participants saw a reference image and a super-resolved reconstruction side byside, and marked every way the reconstruction altered the meaning of the scene: C1 — details ("details"): fine details altered, invented or lost C2 — local structures ("local"): local structures deformed or restructured C3 — holistic semantics ("holistic"): the overall meaning of the scene changes C4 — no change ("none"): nothing meaningful changed C1–C3 may co-occur. C4 is exclusive. Annotators honoured that constraint withouta single exception across all 3,497 judgements. Because one judgement can carryseveral categories, a row is one selected label, not one judgement: a judgementis the set of rows sharing a (user_id, image_id) pair. THE IMAGES 100 real pairs plus 4 attention controls. Each control presents a byte-identicalpair — the same file shown twice — so the only defensible answer is C4. This isverifiable rather than asserted: exactly the four rows flagged is_control = truehave reference_identical_to_reconstruction = true, and no real pair does. The 100 real pairs are balanced 52/52 between two public corpora, LSDIR andFoundIR, and spread across 15 super-resolution models at six or seven pairseach: BSRGAN, DiffBIR, DiT4SR, DiT-SR, FaithDiff, HAT, OSEDiff, PiSA-SR, RAP-SR,RealESRGAN, SeeSR, SUPIR, SwinIR, TSD-SR and TVT. FoundIR pairs span fourdegradation regimes. PARTICIPATION AND QUALITY CONTROL 41 participants started, 29 completed all 104 pairs, and 24 of those passed allfour controls. Controls were graded silently: participants received no feedbackand failing one did not end the session. Nobody who finished scored below two offour, and a missed control was almost always answered "details" — the signatureof someone reading compression noise as real change rather than clicking atrandom. The 24 who passed everything form the clean pool used for the headline results:24 × 100 = 2,400 judgements, exactly 24 per real pair. Every one of thoseparticipants answered every pair, so no result can be an artefact of unevencoverage. CONTENTS annotations.csv 4,700 annotation records manifest_104.csv the 104 pairs with provenance, model, degradation and control flags images/reference/ 104 reference images images/reconstruction/ 104 reconstructions; filename equals image_id README.md column reference, agreement formula, runnable reproduction snippet SHA256SUMS checksums for every file PRIVACY Participants are pseudonymous. IP addresses were removed entirely rather thanhashed, because the IPv4 space is small enough to invert any hash by exhaustivesearch. Timestamps are reduced to dates, with a seconds_from_user_start columnpreserving response-time information without the absolute times that wouldpermit linkage. Country and language values held by fewer than threeparticipants are generalised, so no single row can identify a participant. PROVENANCE AND LICENSING Reference images derive from the public LSDIR and FoundIR datasets and remainunder their original licences; manifest_104.csv records the exact source ofevery file. The reconstructions were generated by the author using the publiccheckpoints of the 15 models listed above. Annotations, manifest anddocumentation are released under CC BY 4.0.

View source

Similar papers

#computer vision Open access Jun 2016

Software Development in Startup Companies: The Greenfield Startup Model

Software startups are newly created companies with no operating history and oriented towards producing cutting-edge products. However, despite the increasing importance of startups in the economy, few scientific studies attempt to address software engineering issues, especially for early-stage startups. If anything, startups need engineering practices of the same level or better than those of larger companies, as their time and resources are more scarce, and one failed project can put them out of business. In this study we aim to improve understanding of the software development strategies employed by startups. We performed this state-of-practice investigation using a grounded theory approach. We packaged the results in the Greenfield Startup Model (GSM), which explains the priority of startups to release the product as quickly as possible. This strategy allows startups to verify product and market fit, and to adjust the product trajectory according to early collected user feedback. The need to shorten time-to-market, by speeding up the development through low-precision engineering activities, is counterbalanced by the need to restructure the product before targeting further growth. The resulting implications of the GSM outline challenges and gaps, pointing out opportunities for future research to develop and validate engineering practices in the startup context.

Carmine Giardino, Nicolò Paternoster, M. Unterkalmsteiner et al. · 179 citations · ⚡14
#computer vision Open access Oct 2016

Software Startups - A Research Agenda

Software startup companies develop innovative, software-intensive products within limited timeframes and with few resources, searching for sustainable and scalable business models. Software startup ...

M. Unterkalmsteiner, P. Abrahamsson, Xiaofeng Wang et al. · 157 citations · ⚡17
#machine learning Review Open access Oct 2016

“Failures” to be celebrated: an analysis of major pivots of software startups

In the context of software startups, project failure is embraced actively and considered crucial to obtain validated learning that can lead to pivots. A pivot is the strategic change of a business concept, product or the different elements of a business model. A better understanding is needed on different types of pivots and different factors that lead to failures and trigger pivots, for software entrepreneurial teams to make better decisions under chaotic and unpredictable environment. Due to the nascent nature of the topic, the existing research and knowledge on the pivots of software startups are very limited. In this study, we aimed at identifying the major types of pivots that software startups make during their startup processes, and highlighting the factors that fail software projects and trigger pivots. To achieve this, we conducted a case survey study based on the secondary data of the major pivots happened in 49 software startups. 10 pivot types and 14 triggering factors were identified. The findings show that customer need pivot is the most common among all pivot types. Together with customer segment pivot, they are common market related pivots. The major product related pivots are zoom-in and technology pivots. Several new pivot types were identified, including market zoom-in, complete and side project pivots. Our study also demonstrates that negative customer reaction and flawed business model are the most common factors that trigger pivots in software startups. Our study extends the research knowledge on software startup pivot types and pivot triggering factors. Meanwhile it provides practical knowledge to software startups, which they can utilize to guide their effective decisions on pivoting.

Sohaib Shahid Bajwa, Xiaofeng Wang, Anh Nguyen-Duc et al. · 127 citations · ⚡15
#computer vision Review Open access May 2015

A survey study on major technical barriers affecting the decision to adopt cloud services

In the context of cloud computing, risks associated with underlying technologies, risks involving service models and outsourcing, and enterprise readiness have been recognized as potential barriers for the adoption. To accelerate cloud adoption, the concrete barriers negatively influencing the adoption decision need to be identified. Our study aims at understanding the impact of technical and security-related barriers on the organizational decision to adopt the cloud. We analyzed data collected through a web survey of 352 individuals working for enterprises consisting of decision makers as well as employees from other levels within an organization. The comparison of adopter and non-adopter sample reveals three potential adoption inhibitor, security, data privacy, and portability. The result from our logistic regression analysis confirms the criticality of the security concern, which results in an up to 26-fold increase in the non-adoption likelihood. Our study underlines the importance of the technical and security perspectives for research investigating the adoption of technology.

Nattakarn Phaphoom, Xiaofeng Wang, S. Samuel et al. · 111 citations · ⚡8
#computer vision Open access Feb 2018

Lean Internal Startups for Software Product Innovation in Large Companies: Enablers and Inhibitors

To compete in this age of disruption, large companies cannot rely on cost efficiency, lead time reduction and quality improvement. They are now looking for ways to innovate like startups. Meanwhile, the awareness and use of the Lean startup approach have grown rapidly amongst the software startup community in recent years. This study investigates how Lean internal startup facilitates software product innovation in large companies and identifies its enablers and inhibitors. A multiple case study approach is followed in the investigation. Two software product innovation projects from two large companies are examined, using a conceptual framework that is based on the method-in-action framework and extended with the previously developed Lean-Internal Corporate Venture model. Seven face-to-face in-depth interviews of the employees with different roles are conducted. Within-case analysis and cross-case comparison are applied to draw the findings from the cases. A generic process flow summarises the common key processes of Lean internal startups. The findings suggest that an internal startup that is initiated management or employees faces different challenges. A list of enablers of applying Lean startup in large companies are identified, including top management support and cross-functional team. Both cases face different inhibitors due to the different process of inception, objective of the team and type of the product. Our contributions are threefold. First, this study is one of the first attempt to investigate the use of Lean startup approach in large companies empirically. Second, the study shows the potential of the method-in-action framework to investigate the Lean startup approach in non-startup context. The third is a general process of Lean internal startup and the evidence of the enablers and inhibitors of implementing it, which are both theory-informed and empirically grounded.

Henry Edison, Nina M. Smørsgård, Xiaofeng Wang et al. · 78 citations · ⚡6
#computer vision Conference Sep 2010

Exploring the Sources of Waste in Kanban Software Development Projects

The application of agile software methods and more recently the integration of Lean practices contribute to the trend of continuous improvement in the software industry. One such area warranting proper empirical evidence is a project’s operational efficiency when using the Kanban method. This short paper takes a new angle and explores waste in the Kanban-driven software development project context. A preliminary research model is presented for helping the consequent replication of the study. The results from the empirical analysis suggest Kanban can be an effective method in visualizing and organizing the current work, but does not prevent waste from creeping in, although the overall project outcome may be successful.

Marko Ikonen, Petri Kettunen, Nilay V. Oza et al. · 67 citations · ⚡9

Related blog posts