👋 Welcome in! 👋
This repository contains the Open Source code for gliff.ai's Scanline Polygon Fill (SLPF) algorithm (based on: Kyle Amoroso’s Polygon Fill Algorithms Benchmark) for use on ANNOTATE.
This repository aims to allow users to fill the area of an annotation object within the ANNOTATE product for the purposes of enhancing their development of imaging AI products. gliff.ai’s SLPF is just one supporting aspect of gliff.ai’s growing privacy-preserving MLOps (Machine Learning Operations) platform. When the full gliff.ai platform is used, gliff.ai’s SLPF provides just one step in developing high-quality and auditable datasets that satisfy any relevant regulatory frameworks which enables our users to build world-changing and trustworthy AI models and products.
✅ We welcome contributions on this repository! ✅
Looking for something specific? 🔍
- Repository Introduction
- Table of Contents
- Installation
- Development
- Linting and Formatting
- Testing
- Contribute
- Contact
- License
Run npm install @gliff-ai/slpf in your command line to install the package from the npm registry.
Frontend code should always be written in Typescript and transpiled using the options in tsconfig.json in this repository. npm should always be used for package management.
npm run serve will run a local webpack developer server for quick access.
As a standard, all code contributions should be linted with ESLint using .eslintrc.js and formatted with Prettier. Note: HTML + CSS, mark-up and mark-down code are exemptions and should be formatted using Prettier but do not need to be linted.
npm run lint will lint the codebase.
Our GitHub Actions will also lint any pull requests before they're merged.
All code contributions should be tested using both the Jest and React Testing Library.
npm run test will run any existing tests in our codebase.
Our GitHub Actions will also test any pull requests before they're merged! These all must pass and have 2 reviewers approval before a pull request can merge. If one or a few fail and your troubleshooting is not giving an answer, please check out the gliff.ai Contribution Guide 👋 for further guidance.
GitHub Actions should only be included under the .github/workflows path.
We welcome all contributors and any contributions on this project through the likes of feedback on or suggesting features and enhancements, raising bug problems, reporting on security vulnerabilities, reviewing code, requesting or creating tests, user testing etc. to ensure gliff.ai can help enable the best and biggest positive impact possible.
Sounds good and want to contribute to the project? 🧑💻
Please check the gliff.ai Contribution Guide 👋 before you get started. Don’t forget the gliff.ai Code of Conduct
A big thank you from the entire gliff.ai team to these fellow contributors (emoji key):
{{Contributor List - coming soon}}
Need some help? 🤔 Have a question? 🧠
Reach out to the gliff.ai team at [email protected] or on our GitHub discussions.
This code is licensed under a GNU AGPLv3 license 📝
Curious about our reasoning for this? Read about them here!