Skip to content

Latest commit

 

History

History
executable file
·
149 lines (115 loc) · 5.43 KB

README.md

File metadata and controls

executable file
·
149 lines (115 loc) · 5.43 KB
Raw

About tudat-feedstock

Feedstock license: BSD-3-Clause

Home: http://tudat.tudelft.nl/

Package license: BSD

Summary: A C++ platform to perform astrodynamics and space research.

Current build status

Azure
VariantStatus
linux_64 variant
osx_64 variant
osx_arm64 variant
win_64 variant

Current release info

Name Downloads Version Platforms
Conda Recipe Conda Downloads Conda Version Conda Platforms

Installing tudat

Installing tudat from the tudat-team channel can be achieved by adding tudat-team to your channels with:

conda config --add channels tudat-team
conda config --set channel_priority strict

Once the tudat-team channel has been enabled, tudat can be installed with conda:

conda install tudat

or with mamba:

mamba install tudat

It is possible to list all of the versions of tudat available on your platform with conda:

conda search tudat --channel tudat-team

or with mamba:

mamba search tudat --channel tudat-team

Alternatively, mamba repoquery may provide more information:

# Search all versions available on your platform:
mamba repoquery search tudat --channel tudat-team

# List packages depending on `tudat`:
mamba repoquery whoneeds tudat --channel tudat-team

# List dependencies of `tudat`:
mamba repoquery depends tudat --channel tudat-team

Updating tudat-feedstock

If you would like to improve the tudat 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 tudat-team channel, whereupon the built conda packages will be available for everybody to install and use from the tudat-team channel. Note that all branches in the tudat-team/tudat-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/number back to 0.

Feedstock Maintainers