---
title: Problem Being Solved
product: ccpem-pipeliner
doc_type: concept
version: main
source: git2docs (code-derived, validation-filtered)
canonical: https://git2docs.com/wabam/docs/ccpem-pipeliner/ccpem-pipeliner/problem-statement
---

# Problem Being Solved

_Why a coordination layer for cryo-EM processing exists and what pipeliner automates_

## Overview

CryoEM data processing involves dozens of heterogeneous programs — motion correction, CTF estimation, particle picking, classification, refinement, model building — each producing outputs that feed into the next step. Coordinating these programs by hand is error-prone, non-reproducible, and difficult to automate at scale. This page explains the coordination problem that CCPEM-Pipeliner solves and the design choices it makes to solve it.

## Related concepts

- **Project structure** — How the project directory is laid out, what `default_pipeline.star` contains, and how sentinel files record job status.
- **Running a processing job** — How to schedule and execute a job using the CLI or the `PipelinerProject` Python API.
- **Building an automated workflow script** — How to chain jobs into a reproducible end-to-end pipeline using `run_schedule` and the `PipelinerProject` API.
- **Writing and registering a custom job plugin** — How to create a new job type as a Python class and register it under the `ccpem_pipeliner.jobs` entry-point group.
- **Viewing results in Doppio or RELION GUI** — How projects created by pipeliner are compatible with graphical interfaces for interactive inspection and continuation.
- **Install and verify pipeliner** — How to install `ccpem-pipeliner` with pip and run `pipeliner.check_setup` to confirm that required external programs are available.
