Feedstock license: BSD-3-Clause
Home: http://spectral-cube.readthedocs.io
Package license: BSD-3-Clause
Summary: A package for interaction with spectral cubes
Development: https://github.com/radio-astro-tools/spectral-cube
Documentation: http://spectral-cube.readthedocs.io
The spectral-cube package provides an easy way to read, manipulate, analyze, and write data cubes with two positional dimensions and one spectral dimension, optionally with Stokes parameters. It provides a uniform interface to spectral cubes, robust to the wide range of conventions of axis order, spatial projections, and spectral units that exist in the wild. It also allows easy extraction of cube sub-regions using physical coordinates and the ability to easily create, combine, and apply masks to datasets. It is designed to work with datasets too large to load into memory.
| All platforms: |
|
| Name | Downloads | Version | Platforms |
|---|---|---|---|
 |
 |
 |
 |
Installing spectral-cube from the conda-forge channel can be achieved by adding conda-forge to your channels with:
conda config --add channels conda-forge
conda config --set channel_priority strict
Once the conda-forge channel has been enabled, spectral-cube can be installed with conda:
conda install spectral-cube
or with mamba:
mamba install spectral-cube
It is possible to list all of the versions of spectral-cube available on your platform with conda:
conda search spectral-cube --channel conda-forge
or with mamba:
mamba search spectral-cube --channel conda-forge
Alternatively, mamba repoquery may provide more information:
# Search all versions available on your platform:
mamba repoquery search spectral-cube --channel conda-forge
# List packages depending on `spectral-cube`:
mamba repoquery whoneeds spectral-cube --channel conda-forge
# List dependencies of `spectral-cube`:
mamba repoquery depends spectral-cube --channel conda-forge
conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.
A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by Azure, GitHub, CircleCI, AppVeyor, Drone, and TravisCI it is possible to build and upload installable packages to the conda-forge anaconda.org channel for Linux, Windows and OSX respectively.
To manage the continuous integration and simplify feedstock maintenance
conda-smithy has been developed.
Using the conda-forge.yml within this repository, it is possible to re-render all of
this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.
For more information please check the conda-forge documentation.
feedstock - the conda recipe (raw material), supporting scripts and CI configuration.
conda-smithy - the tool which helps orchestrate the feedstock.
Its primary use is in the construction of the CI .yml files
and simplify the management of many feedstocks.
conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)
If you would like to improve the spectral-cube recipe or build a new
package version, please fork this repository and submit a PR. Upon submission,
your changes will be run on the appropriate platforms to give the reviewer an
opportunity to confirm that the changes result in a successful build. Once
merged, the recipe will be re-built and uploaded automatically to the
conda-forge channel, whereupon the built conda packages will be available for
everybody to install and use from the conda-forge channel.
Note that all branches in the conda-forge/spectral-cube-feedstock are
immediately built and any created packages are uploaded, so PRs should be based
on branches in forks and branches in the main repository should only be used to
build distinct package versions.
In order to produce a uniquely identifiable distribution:
- If the version of a package is not being increased, please add or increase
the
build/number. - If the version of a package is being increased, please remember to return
the
build/numberback to 0.