Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PathPlanner: Consider Levels #11

Open
Elscha opened this issue Dec 14, 2023 · 1 comment
Open

PathPlanner: Consider Levels #11

Elscha opened this issue Dec 14, 2023 · 1 comment
Assignees

Comments

@Elscha
Copy link
Contributor

Elscha commented Dec 14, 2023

Actual Situation

Skills have an attribute level, which is currently ignored by the algorithm.

Target Situation

The level should implicitly refer to a taxonomy, which the user has into his mind, e.g., Bloom taxonomy. With this in mind, the user may create multiple skills with the same name, but with different levels. Higher levels include automatically all lower levels of the same name (w.r.t. the Repository that defines the Skills).

Image

Purpose

User may define the "same" Skills (same name) multiple times, on different Levels and may assign them to separate LearningUnits. For instance:

  • LOOPS (APPLY): The user can use for, while, do while, for each
  • LOOPS (EVALUATE): The user may choose which kind of loops fits best for a given situation
  • Not all levels must be assigned. In this case, there are no Skills such as LOOPS (REMEMBER), LOOPS (UNDERSTAND), ... but they may be created if necessary.

Modifications to the Algorithm

The algorithm must check if a Skill at least on the specified level is fulfilled. If the Skill was already learned on a higher level then specified, the user does not need to learn also the lower level again.

@AhmadAlamoush
Copy link
Contributor

Points from our meeting on the Skill Levels:

  • We need a property in the Skill to hold the ID that matches the skill levels for the same skill. It can be the name of the skill (In case we guarantee the name matching during the creation of the skills), or it can be a unique ID.

  • We use that ID to retrieve all levels for the same skill. For example, we use ID= 2 from the Skill A (Level 1) to get all skill levels with ID= 2.
    image

  • A skill level can learned by a combination of different skill levels as children. For example, Skill A (Level 3) can learned by learning Skill B (level 1), Skill C (level 3), Skill D (level 3), and Skill D (level 2).

image

  • We should consider the level of the skills in the goals during the path planner algorithm to find a learning path.

A discussion point,

  • What if the requested skill level (goal skill level) does not exist?
  • What if a learning path is missing a skill with specific level?
  1. Propose a higher level of the same skill since it includes the lower skill. Keep in mind, that the higher level of a skill gives more depth about the subject.
  2. No path found for the requested skill level since other levels give more or less depth about the subject.

@kschmid

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants