-
Notifications
You must be signed in to change notification settings - Fork 9
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #671 from nsidc/cleanup-environments
Lock "command" environment
- Loading branch information
Showing
11 changed files
with
2,026 additions
and
228 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
# QGreenland's `conda` environments | ||
|
||
QGreenland has many pieces that require different dependencies, and those are defined in | ||
these different environments. | ||
|
||
Environments are defined in `environment.yml` files, and pinned to allow packages to | ||
upgrade over time without too much unexpected breakage. Environments are locked in | ||
`conda-lock.yml` files with exact pins and checksums for reproducibility. | ||
|
||
|
||
## Locking | ||
|
||
In any directory containing an `environment.yml` file, run `conda-lock` to lock that | ||
environment. | ||
|
||
|
||
## Notes | ||
|
||
The `main` and `command` environments are only locked for the `linux-64` platform | ||
because it's expected that they will only be used in a Linux container context. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
# QGreenland's "command" `conda` environment | ||
|
||
This environment exists for running `CommandStep` layer data processing steps. | ||
|
||
The original rationale for creation of this environment was conflict between | ||
QGreenland's [main environment](/environments/main/README.md) dependencies and | ||
dependencies needed for layer data processing. | ||
|
||
|
||
## TODO | ||
|
||
* Ideally all data processing, including Python steps, would run in this environment for | ||
reproducibility. When that's implemented, consider renaming this environment to the | ||
"step" environment? In the long term, we may consider extracting the framework | ||
elements to a library, and in that case we'd want the end-user to define data | ||
processing steps, and the dependencies required to execute those steps, preferably | ||
with a lock-file defining the exact environment that was _actually_ used. So this | ||
pattern of defining a data-processing lock-file is probably here to stay. |
Oops, something went wrong.