Skip to content

check two-level scenario #28

Open
monkey0head opened this issue Nov 1, 2021 · 2 comments
Open

check two-level scenario #28

monkey0head opened this issue Nov 1, 2021 · 2 comments
Assignees
Labels
Projects

Comments

@monkey0head
Copy link
Contributor

  • check for bugs/errors
  • create jupyter notebook illustrating two-level scenario usage and optimisation
@monkey0head monkey0head added this to Backlog in Kanban via automation Nov 1, 2021
@Darel13712 Darel13712 added the help wanted Extra attention is needed label Nov 15, 2021
@AleXXL1986
Copy link
Collaborator

check for bugs/errors means that you should to execute it and check adequacy of results

@monkey0head monkey0head moved this from Backlog to To Do in Kanban Dec 14, 2021
@monkey0head
Copy link
Contributor Author

  • split scenario into stages (classes and functions) to be able to construct a pipeline from those stages (two-stages scenario with distributed lama) or use individually
  • check each stage logic and look for bugs
  • create notebook showing stages execution one-by-one and comparing quality metrics of two-stages and first-stage models

@monkey0head monkey0head moved this from To Do to In Progress in Kanban Jan 28, 2022
@monkey0head monkey0head self-assigned this Jan 28, 2022
@monkey0head monkey0head added in_progress wip and removed help wanted Extra attention is needed labels Jan 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
Kanban
In Progress
Development

No branches or pull requests

3 participants