LEAP-Systems / LEAP-Systems/api

Support for Processor Order of Operations

Open
#18 0 comments 0 reactions 1 assignee View on GitHub

@ztnel is already working on this.

Since Aug 31, 2021.

enhancement model
Dominant language
Python
Stars
0
Forks
0
No merged PRs in 30d

Description

Description

Currently, the processor has a fixed non-configurable order of operations when it comes to applying image processing techniques. This needs to be supported as the order greatly affects the resulting image. All the embedded documents could have an index field to log the order of ops:

{
   "gaussian_blur": {
      "index": 1,
      "kernel_width": 3,
      "kernel_height": 3
   },
   "dialation": {
      "index": 2,
      "kernel_width": 3,
      "kernel_height": 3,
      "iterations": 20
   }, 
   "erosion": {
      "index": 0,
      "kernel_width": 3,
      "kernel_height": 3,
      "iterations": 20
   },
}

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.