- You will need an installation of
conda. I recommendminiforge3 - Run
make install - Check your installation by running
make test
- NOTE: For now, many of these are likely to fail during the code transition
You should be good to go! Make sure to conda activate kl-tools whenever you want to run or develop the code.
Until more comprehensive documentation is written, please checkout notebooks/getting_started.py in this repo.
If you need a package that does not currently exist in the kl-tools, do the following:
- Make sure you're in the
kl-toolsenvironment conda install {your-package}conda export --no-builds --from-history -f environment.yamlgit add environment.yamlon your branch- Merge in PR after it's been approved
- Inform other users that they likely need to rerun
make installduring their next pull, likely on slack
NOTE: This will be streamlined once we have our scripts setup for conda-lock.
We are just getting started using kl-tools as a larger group. Let's stick to the following guidelines:
- Low threshold for posting issues - let's help one another!
- No pushing to
mainwithout a PR - please work on a branch (ideally in the format of{user}/{branch-name}) and submit a pull request with a reviewer tagged. Default is @sweverett. - Keep most branches focused on a single issue and with a short lifetime. Let's merge in features quickly and not leave branches (or PRs) dangling.
- Until we have CI (continuous integration) setup, please make sure the unit tests run on your branch before sumitting a PR. Do this by running
make test.