# 📂 Execution Outputs and Logs

Every method executed through CCP generates a set of output files.  
These include both **logs produced by the system** and **results generated by the method itself**.

All outputs are collected in the final archive and can also be inspected through the Execution Monitor.

---

## 📁 Where Outputs Are Stored

All output files must be written by the method to the `/ccp_data/` directory inside the container.  
At the end of the execution, this directory is compressed into `output.zip` and attached to the execution record.

Common examples:

```sh
/ccp_data/ 
├── report.txt 
├── results.tiff 
├── metrics.json 
├── outputs_stdout.<id>.txt 
├── outputs_stderr.<id>.txt 
└── outputs_ccp-entrypoint.sh
```

---

## 🖥️ System-Generated Logs

Some outputs are automatically created by the execution environment:

- **`outputs_stdout.<id>.txt`**: standard output (e.g. `print()` or `echo`)
- **`outputs_stderr.<id>.txt`**: standard error (warnings, exceptions)
- **`outputs_ccpenv`**: snapshot of environment variables at runtime
- **`outputs_ccp-entrypoint.sh`**: merged script of deploy + execute phases

These files are useful for debugging or understanding how the method was run.

---

## 📦 Method Results

Depending on what your method produces, outputs may include:

- Text files (e.g., `summary.txt`, `report.csv`)
- Visuals (e.g., `plot.png`, `wordcloud.jpg`)
- Geospatial files (e.g., `.tiff`, `.shp`, `.geojson`)
- Structured data (e.g., `.json`, `.xml`)

These are typically written by your script and defined in the `method.json` under the `outputs` section.

---

## 🗄️ Archive Options

When submitting a method execution, you can choose what to archive:

- **Full provenance**: logs + results + all metadata
- **Outputs only**: results without metadata
- **No archive**: files are temporary and deleted after download

This setting affects whether the execution is saved in your workspace and how results are packaged.

---

## 🔗 Related Pages

- ⏯️ [Understanding executions](./01_executions)

- 🌀 [Execution status and lifecycle](./03_execution_status)

- 📑 [Generated metadata files](./04_metadata_files)

- 🚦 [Execution Monitor](/02_ccp_interface/04_execution_monitor)