For cuisto-related issues, you can open an issue here
explaining your issue. Please provide as much relevant information as you can, such as platform, Python version, cuisto version, data sample and code snippets to help reproduce the issues.
You can also use the Issues to ask questions. We'll try to get back to you as soon as possible.
For QuPath and/or ABBA-related issues and questions, you can find support over at the image.sc forum.
You can contribute a fix or a new feature to this project with the following steps:
- Create a conda environment with Python 3.12
conda create -n cuisto-dev python=3.12- Fork the project on GitHub.
- Clone the project
git clone https://github.com/<your-github-username>/cuisto- Activate the environement and install the package in editable mode, with the development dependencies
conda activate cuisto-dev
pip install -e .[doc,dev]- Make a new git branch where you will apply the changes
git checkout -b your-branch-name- Make your changes and test them. You can add tests in the
testsfolder and run them withpytest. Once done,git add,git commitandgit pushthe changes. - Make a Pull Request from your branch to the cuisto repository.
Python code should be PEP8 compliant. We use ruff with a line length of 88 to format the code.
Docstrings are formatted with the numpy convention.
We use camelCase for file and variable names. The scripts should contain a docstring with the filename and a short description of what it does. See an existing example.
The documentation is written in Markdown, using mkdocs and mkdocs-material.
See the existing pages to know how to format things, including :
- `code` for code snippets,
/file/pathsandscriptName.groovy. The latter should contain a backlink to the actual file in the Github repository.