snap-contrib / snap-conda

SNAP as a conda package

SNAP as a conda package

A package manager is a tool that automates the process of installing, updating, and removing packages. Conda, with its "conda install", "conda update", and "conda remove" sub-commands, falls squarely under this definition.

Conda is a general-purpose package management system, designed to build and manage software of any type from any language. As such, it also works well with Python packages.

Conda is a language-agnostic cross-platform environment manager that installs any package within conda environments.

This repository provides a conda recipe for packaging SNAP as a conda package.

The goal of SNAP as a conda package is to ease the unattended installation of SNAP and snappy in headless environments such as Linux consoles or docker images.

This goal is achieved by creating conda packages installing SNAP and snappy, published on a public conda channel.

Building this recipe

This recipe is built with conda (or mamba) with:

conda build -c terradue .

Installing SNAP as a conda package

To install SNAP as a conda package on Linux, use conda (or mamba):

conda install -c terradue -c conda-forge snap=8.0.0

Limitations

SNAP as a conda package can be installed on Linux. For Mac or Windows, we suggest looking at the proposed startegies:

• https://github.com/snap-contrib/cwl-snap-graph-runner to use CWL and Docker to process GPT graphs
• https://github.com/snap-contrib/vscode-remote-snap to use Visual Studio Code remote containers to develop SNAP and Snappy based Python applications (Windows 10 PRO or Mac OSX)

snap-conda's Issues

java conda package dependency cannot be pinned

Pinning the java conda package breaks the installation.

unpin the java conda package build number

Update for SNAP 9.0.0

Is there any chance to upgrade to version 9.0.0? I use it frequently with google colab and the environment is no longer backwards compatible. My thanks and congratulations on your work!

conda-forge build?

I started the process to create a conda-forge version of this repo: https://github.com/ryan-salo/staged-recipes/tree/esa-snap.

However, I'm hitting an error with fonts not found during the update command and it enters into a never ending loop. Any tips on how to satisfy that dependency? I tried adding some env vars and fonts packages, but that didn't work. I also moved the post-link.sh content to build.sh, I wasn't able to see the error until I did that.

`auxdata` directory per user not per environment

Hi @fabricebrito,
thanks for your work on this conda version of SNAP! I think it's a very valuable development.
I've just started testing it on our university's HPC cluster and it seems to work quite well. One issue I've noticed is the usage of the default .snap directory and the auxdata subdirectory relative to the SNAP installation inside of an environment. It would be much better to set these once for the user, which would avoid the download and accumulation of auxiliary data (DEM, orbit files, etc) each time you start with a new conda environment.

I was able to adjust some configurations to change the default directories, as described here and here. You could also have a look how pyroSAR handles this, as it uses a .snap user directory by default.

What do you think?

Cheers,
Marco