ArtifactsACSOS 2026

Accepted Artifacts

Camera Ready Submission

Camera Ready Submission for Companion Proceedings - Artifacts

STEP 1: Important Dates

At least one author per accepted artifact standalone paper must complete author registration by July 20, 2026.

Final camera-ready manuscripts must be submitted by July 20, 2026 AoE.

STEP 2: Page Limits

STEP 3: Formatting Your Paper

• Submitted abstracts should not exceed 200 words.
• Final submissions must use US Letter page size, the two-column IEEE conference proceedings format, and PDF format.
• IEEE templates are available from the IEEE Author Center: https://www.ieee.org/conferences/publishing/templates.html
• Do not include page numbers, headers, or footers.
• The camera-ready version must include author names, affiliations, and acknowledgments as appropriate.

STEP 4: Submitting Your Final Version

Once the format of your paper has been verified and validated, you may submit your final version.

All papers should be submitted using the submission system provided by the IEEE Author Submission Site. Please use the correct site for your proceedings volume:

• Artifact Standalone Papers: ACSOS-C Author Submission Site: The IEEE Author Submission Site link will be provided directly to authors of accepted papers by the corresponding track chairs.

After you login to the IEEE Author Submission Site, please follow the instructions as you click the Next button on the top right corner of the site. Please enter the following information exactly as it appears on your paper:

• Paper ID (Paper ID from EasyChair, unless CPS assigns a different ID)
• Names of authors, affiliations, countries, and email addresses
• Title and abstract

Follow the instructions to submit your final manuscript.

STEP 5: Submitting a Signed Copyright Release Form

ACSOS 2026 requires authors to submit a fully digital version of the electronic IEEE Copyright-release Form (eCF). The eCF is provided at the IEEE Author Submission Site.

Follow the instructions in the IEEE Author Submission Site to properly fill out and submit the IEEE Copyright-release Form (eCF), including:

• Paper's full title
• All author names
• Conference title:
  • 2026 IEEE International Conference on Autonomic Computing and Self-Organizing Systems Companion (ACSOS-C)
• Signature on the appropriate line

The signed IEEE Copyright-release Form (eCF) should be submitted together with your camera-ready manuscript by July 20, 2026 AoE.

If you have any questions about the above procedures, please contact the Proceedings Chair: Jialong Li (lijialong@aoni.waseda.jp).

Note: Extra pages are not allowed unless explicitly stated by the conference organizers. Please complete each of the above steps. The conference organizers will not be responsible if your paper is omitted from the proceedings, is not available online in IEEE Xplore, or is subject to additional processing costs if these steps are not performed.

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.

Submissions

ACSOS 2026 requests submissions of two types of artifacts:

1. Artifact standalone paper, and
2. Artifact from a paper.

An artifact standalone paper comprises two parts: an artifact paper (max 6 pages, including references) and the artifact itself. The artifact paper should summarize the research problem, the research challenges in relation to system autonomy or the concrete self-* properties that the artifact addresses. The artifact papers have to adhere to IEEE formatting instructions.

Additionally, in the Artifact Track, we also aim to review and promote research artifacts from papers that were previously accepted as part of the Research Track. Namely, authors that have a paper accepted as part of ACSOS 2026 can submit only their artifact for review within the Artifact Track.

The artifacts in both cases are expected to be prepared according to the IEEE Artifact Reproducibility Badges Policy and have a well-documented usage of the artifact. The badges will also be visible in the electronic versions of the papers in the IEEE Xplore document on the top-right of the page to denote the availability of the artifact. Please note that in the case of an artifact from a paper, the badge will be assigned to the research paper. Depending on the type of artifact, the papers will be assigned with either Code Reviewed and Dataset Reviewed badges.

Papers should be submitted via EasyChair. The papers should also contain a link from where the reviewers can access and download the artifact. Please note that at this stage, it does not need to be a link to the permanent repository. In case of artifact submissions from papers, we request the authors, upon submission of the artifact, to submit the pre-print or the submitted version of their accepted paper in which the artifact is used and, ideally, detailed and described in some of the sections of the paper. Artifacts must not have been previously published or concurrently submitted elsewhere.

The standalone artifact papers will be published in the conference proceedings companion. Additionally, the accepted artifacts from both the standalone artifact papers and published research papers will be given a chance to present their artifact at ACSOS 2026.

Preparing the Artifact for Submission

Authors must perform the following steps to submit an artifact.

Note that the artifacts submission will follow a single-blinded review process (there is no need to anonymize your submission).

Preparing the Artifact

While preparing the artifact, the authors need to prepare an installation package so the artifact can be installed and executed in the environment used by the reviewer. It is important that the documentation, e.g., the README.md in the artifact repository, provide sufficient information and instructions so that the reviewers with computer science background and reasonable knowledge of scripting and build tools can install, build, and run the artifact. When preparing the artifact, it is important to keep in mind: the accessibility of the artifact to other researchers and the fact that the artifact reviewers have very limited time to assess each artifact. Therefore, the setup for your artifact should take less than 20 minutes, or it is unlikely to be endorsed simply because the committee will not have sufficient time to evaluate it.

Suppose the artifact contains or requires the use of special tools or software. In that case, the authors must provide the artifact with a working environment in a virtual image (e.g., using Oracle Virtual Box) or a Docker container image. Therefore, the code should run on all three major platforms (Mac, Win, Linux) either natively or using Docker/VM. If designed for mobile applications, instructions should be clear and concise to assist reproducibility on the appropriate platform during the artifact review process. Alternatively, authors can provide a link to a web service that allows reviewers to execute the artifact (e.g., using Jupyter notebooks). In any case, the artifact should be exercisable and appropriately validated by reviewers; otherwise, it may be desk-rejected.

Making the Artifact Available

Upon submission,authors need to make sure that the artifact is publicly available for download under an open-source license so that the reviewers can access it. We suggest a link to a public repository, e.g., on GitHub under GPL. If the artifact contains large datasets or VM images, we recommend using open (commercial) archival repositories that guarantee long-time storage, e.g., figshare and Zenodo. We encourage the authors to use repositories dedicated to data sharing where no registration is necessary for those accessing the artifacts (e.g., please avoid using services such as GoogleDrive). The artifacts accepted to the ACSOS 2026 must be made permanently available to the public by the time the camera-ready version of the paper is due. ACSOS 2026 reserves the right to archive artifacts to a central repository or ACSOS artifact webpage in the future.

Documenting the Artifact

The artifact should be complete and carefully documented. We summarize the requirements for documenting the artifact in the following.

The paper should include a link to a short video (YouTube, max. 5 minutes) demonstrating the artifact.

The artifact must be self-contained, meaning it contains the artifact itself, which may include source code, executables, data, a virtual machine image, documents, and other content deemed relevant by the authors.

The artifact must include documentation that describes the artifact. Namely, the authors need to write and submit documentation explaining how to obtain the artifact package, how to unpack the artifact, how to get started, and how to use the artifacts in more detail. The entry point to the documentation should be easy to identify (e.g., README.md or index.html file in the top-level directory of the artifact). The documentation should contain:

• A Getting Started section in which the authors summarize the key elements of the artifact, which ideally enable the reviewers to run, execute or analyze the artifact without technical difficulty. The requirements and the artifact limitations should be discussed. If applicable, descriptions of how the artifact can be customized and extended to be reused in different research contexts.
• Step-by-step instructions on how to download, install, run, configure and execute the artifact, including how to check the results of the execution. These instructions should also show how the authors propose evaluating the artifact and how a new user can get started with the artifact. If applicable, descriptions of how the artifact can be customized and extended to be reused in different research contexts. And lastly, if the installation of the artifact includes multiple steps, then we expect the authors to provide scripts that automate the build and install process or to provide a virtual image or a Docker container image.
• Where appropriate, descriptions of different sub-components of the artifacts, architectures, design diagrams, and figures shall be provided that assist the comprehension and evaluation of the artifact.
• A license file or statement describing the distribution rights. Note that a reusable artifact requires some kind of open-source license.

Awardable Badges

The artifacts submitted to the conference will be evaluated and receive the corresponding badges, as follows. To be awarded one of the badges, the submitted artifact should provide the necessary information for reviewers to verify the submitted work.

Available:

The code and/or datasets, including any associated data and documentation, provided by the authors is reasonable and complete and can potentially be used to support reproducibility of the published results. The artifact submission should contain a link to the code/dataset on a public repository (e.g., GitHub, Zenodo), where reviewers can check and download the code/dataset.

Reviewed:

The code and/or datasets, including any associated data and documentation, provided by the authors is reasonable and complete, runs to produce the outputs described, and can support reproducibility of the published results. To obtain these badges the code/dataset provided should run/be accessible without major configuration or modification of the tool.

Reproducible:

This badge signals that an additional step was taken or facilitated to certify that an independent party has regenerated computational results using the author-created research objects, methods, code, and conditions of analysis. Reproducible assumes that the research objects were also reviewed. The artifact submission should include an experiment (together with all results) such that reviewers can easily compare the obtained results from those reported, within reasonable time.