# Sandbox paths and pipeline mappings

## Sandbox paths and their bucket locations and mappings

The table below provides the sandbox (interval/IVM) paths, their "mappings", external bucket paths and their descriptions. If using these paths for running pipelines (e.g. setting file or folder locations in analysis input .json files), the Sandbox (IVM) path **will not work** and only the sandbox mapping and external bucket paths can be used for this purpose.

<table><thead><tr><th width="220">Sandbox (IVM) path</th><th width="174">Sandbox mapping</th><th width="171">External bucket path</th><th>Description</th></tr></thead><tbody><tr><td><code>/finngen/library-green/</code></td><td><code>LIBRARY_GREEN/</code> </td><td><code>gs://finngen-production-library-green/</code></td><td>FinnGen's core analysis results, summary data, <a href="../../../working-outside-the-sandbox/green-library-data">anonymous data</a></td></tr><tr><td><code>/finngen/library-red/</code></td><td><code>LIBRARY_RED/</code></td><td><code>gs://finngen-production-library-red/</code></td><td>Phenotype, Genotype data, <a href="../../../finngen-data-specifics/red-library-data-individual-level-data">individual-level data</a></td></tr><tr><td><code>/finngen/green/</code></td><td><code>SANDBOX_GREEN/</code></td><td><code>gs://fg-production-sandbox-Y_green/</code></td><td>Researchers' own <a href="../../quirks-and-features/how-to-upload-to-your-own-ivm-via-finngen-green">uploaded data</a>.</td></tr><tr><td><code>/finngen/red/</code></td><td><code>SANDBOX_RED/</code></td><td><code>gs://fg-production-sandbox-Y-red/</code></td><td>Researchers' own analysis results, the <a href="../../../quirks-and-features/sharing-individual-level-data-within-the-sandbox#sharing-within-your-organization">organization's own "red" bucket</a></td></tr><tr><td><code>/finngen/pipelines/</code></td><td><code>SANDBOX_PIPELINE/</code> </td><td><code>gs://fg-production-sandbox-Y-pipeline/</code></td><td><a href="../../which-tools-are-available/pipelines">Pipeline</a> results.</td></tr><tr><td><code>/home/ivm/</code></td><td>NA</td><td>NA</td><td>Home disk. Users' personal data and scripts. Cannot be accessed </td></tr><tr><td><code>/finngen/shared/</code></td><td><code>LIBRARY_SHARED/</code></td><td><code>gs://finngen-production-library-shared/</code></td><td><a href="../../../quirks-and-features/sharing-individual-level-data-within-the-sandbox#sharing-outside-your-organization">Shared data between all Sandboxes</a> (organizations)</td></tr><tr><td><code>/finngen/library-green/finngen_RX/unmodifiable_pipelines/</code></td><td><code>CUSTOM_GWAS/</code></td><td><code>gs://library_green/finngen_RX/unmodifiable_pipeline/</code></td><td>Output location of unmodifiable pipeline results.</td></tr></tbody></table>

**Note 1**. The green, red and pipelines buckets (`/finngen/green/`, `/finngen/red/` and `/finngen/pipelines/`)  are specific to your organisation's bucket and data in these locations cannot be seen by other organisations. If using the external (bucket) path to access these locations, **you will need to replace the letter `Y` with the number of your Sandbox**. If you do not know your organisation's sandbox number, you can find it from the green, red and pipelines bucket paths in a file named `buckets.txt` on your sandbox desktop.

**Note 2**. For unmodifiable pipeline results, **remember to replace the letter `X` in the sandbox or external path with the release number of the unmodifiable pipeline** (e.g. `12`).

**Note 3**. The [greendownloads](https://docs.finngen.fi/working-in-the-sandbox/quirks-and-features/how-to-download-results-from-your-ivm) or the [greenuploads](https://docs.finngen.fi/working-in-the-sandbox/quirks-and-features/how-to-upload-to-your-own-ivm-via-finngen-green) buckets are not accessible from the Sandbox.

## Finding bucket paths and mappings within sandbox

You can remind yourself of your organisation's Sandbox number and their buckets paths from the `buckets.txt` file on the Sandbox desktop (see [Navigating the Sandbox](https://docs.finngen.fi/working-in-the-sandbox/quirks-and-features/navigating-the-sandbox)) - the full path of this file is `/home/ivm/Desktop/buckets.txt`.

The full bucket paths are also stored in environment variables in your terminal environment. For example, to see the bucket paths of the red and pipeline buckets in the terminal, you can use the `echo` command:

`echo $RED_BUCKET`

`echo $PIPELINE_BUCKET`

<figure><img src="https://3072695768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhYL0UTLjqsuIdK0SSO%2Fuploads%2Fgit-blob-b1bb0f1f4628edd602aee5d5efd56dd27e42f7a4%2Fimage%20(616).png?alt=media" alt=""><figcaption></figcaption></figure>

and use `$RED_BUCKET` and `$PIPELINE_BUCKET` to refer those paths within the terminal when performing file operations (e.g. copying, moving, deleting etc.) using the `gsutil` command.

## Copying files to your organisation's red bucket

In order to make files accessible for running analyses in the cloud (e.g. any pipeline submitted using the [Pipelines](https://docs.finngen.fi/working-in-the-sandbox/which-tools-are-available/pipelines) tool), the files first need to be copied to a externally accessible location. For this purpose, the best location is the red bucket, which is specific to each organisation's sandbox environment and can be used to store red (individual-level) or green (summary-level) data. To copy a file to the red bucket, open the terminal ("Terminal Emulator" from the Applications menu) and run the command:

`gsutil cp /path/to/file_to_copy.txt $RED_BUCKET/username/`&#x20;

where `/path/to/file_to_copy.txt` is the full sandbox path of the file you want to copy and `username` is your sandbox username. If the folder `$RED_BUCKET/` doesn't already exist, this command will create it.

To use this file for analyses submitted to the cloud, the path you would need for the input .json file would therefore be `SANDBOX_RED/username/file_to_copy.txt`, using the mapping format.

It is recommended that you copy files only to your own red bucket folder (i.e. `$RED_BUCKET/username/`) so that you don't accidentally overwrite other users' files and also that you can find the files again when needed. It is good practice to create subfolders within your own red bucket folder to keep your files organised, e.g. by copying the required files to a specific subfolders. An example could be:

`gsutil cp /path/to/myphenotypes.txt.gz $RED_BUCKET/username/Phenotype_data/R12/`&#x20;