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

Feat/topsis risk assessment #76

Merged
merged 16 commits into from
Oct 10, 2023
Merged

Feat/topsis risk assessment #76

merged 16 commits into from
Oct 10, 2023

Conversation

FredericDymko
Copy link
Collaborator

No description provided.

@FredericDymko FredericDymko force-pushed the feat/topsis_risk_assessment branch from 62fdcdc to 8e26cfe Compare September 22, 2023 07:09

3. To add a new criterion, create a new Python class that inherits from the abstract class Criterion defined in "criterion.py." The class should implement the following methods:
- `get_name()`: This method should return the name used to retrieve the criterion's values using the `get_data` method.
- `get_direction()`: Return a constant that indicates whether the criterion should be maximized or minimized. You can use `mt.Math.TOPSIS.MAX` or `mt.Math.TOPSIS.MIN` from the provided mt module.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Explain which one should be chosen in which cases

@Creadeyh Creadeyh merged commit ad02adf into devel Oct 10, 2023
@Creadeyh Creadeyh deleted the feat/topsis_risk_assessment branch October 10, 2023 13:46
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

Successfully merging this pull request may close these issues.

3 participants