ArtifactsACSOS 2026

Call for Artifacts

ACSOS 2026 will offer a dedicated artifact track. Our aim is to encourage the community to build high-quality artifacts that support evaluating novel approaches, methods, or applications for autonomic and self-* systems that can also be reused, shared and extended by other researchers. Our long-term goal is to establish a collection of reusable evaluation setups and case studies. Creating and maintaining a catalog of artifacts will also support discussing, comparing and assessing the research conducted in this community.

### Types of artifacts

ACSOS’s definition of artifacts is inspired by the ACM definition, which defines an artifact as “a digital object that was either created by the authors to be used as part of the study or generated by the experiment itself. For example, artifacts can be software systems, scripts used to run experiments, input datasets, raw data collected in the experiment, or scripts used to analyze results.” In particular, we are interested but not limited to:

• Software systems: including implementation testbeds or exemplars. We are looking for both simulated software systems and software deployable on real hardware, as well as mobile applications. These systems should highlight the specificities in the requirements, specifications, design, implementation, testing, and validation relevant to engineering self-* and autonomic systems or present challenges that these systems address.
• Frameworks that potentially include tools and services that illustrate and implement new approaches, techniques, or algorithms for self-* and autonomic systems.
• Data and datasets that include, e.g., logging data, system traces, sensor data, or raw survey data that can support various phases of the engineering process of self-* and autonomic systems.

This list is not exhaustive; authors with questions about the suitability of an artifact should reach out to the chairs. Additionally, the published artifact papers will be associated with IEEE Reproducibility Badges in the conference program and conference proceedings. All information about the badging and the required processes for preparing the artifact is available in the Submissions tab.

Submission Types

In ACSOS 2026, we call for two kinds of artifact submissions:

• Artifact standalone paper: consists of (1) an artifact paper (max 6 pages, including references), and (2) the artifact itself. The standalone artifact papers will be published in the conference proceedings companion.
• Artifact from a paper accepted in the main ACSOS research track: only the artifact has to be submitted, and badges will be associated with the original research paper. For this type of submission, we recommend to check the “I intend to submit a companion artifact in case of acceptance” checkbox when you submit your paper to the main track.

The best artifact will be issued an award during the conference.

Important Dates

All times in Anywhere on Earth (AoE) timezone.
For more information on the artifacts submission to ACSOS 2026, please refer to the Submission tab.

Artifact Review Process and Selection Criteria

All submitted artifacts will be thoroughly evaluated by multiple reviewers of the artifact program committee. Each artifact will be evaluated according to the expectations set up 1) by the documentation of the artifact, and 2) by the artifact paper (in artifact standalone papers) or the paper (in artifact from a paper). In addition to just running the artifact, the reviewers may try to tweak provided inputs and create new ones, to test the limits of the system. Artifacts will be evaluated according to the following criteria:

1. Understandability: Is the artifact easy to understand? Does the artifact identify and address a gap in the existing works and literature? Is the contribution of the artifact clearly explained?
2. Timeliness: Does the artifact address a problem that is timely? Is this value clearly explained in the paper?
3. Usability: Is the artifact executable: easy to download, install, configure and execute? Is the artifact operational: functional and usable? Can the artifact be reused by other researchers?
4. Quality of documentation: Is the artifact well-documented and structured? Is the readme of the artifact repository sufficient to run and execute the artifact? Does the documentation include the minimum system and environment requirements for usage (e.g., OS, CPU, RAM, GPU, Disk)? Are the limitations of the artifact identified and visibly documented?
5. Quality of code: Is the code of the artifact readable and well-commented?

The key benefit of investing the considerable work required to get an artifact published at ACSOS is the constant reuse of it by the community, which leads to a broader and larger impact of the work.