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

Fix issue 181 #189

Merged
merged 48 commits into from
Sep 1, 2023
Merged

Fix issue 181 #189

merged 48 commits into from
Sep 1, 2023

Conversation

SarahAlidoost
Copy link
Member

@SarahAlidoost SarahAlidoost commented Jul 7, 2023

Description

closes #181, the merge is pending addressing issues mentioned here. This branch re-produces the same results as those generated by the main branch, tested with a small dataset.

Checklist

  • Add a reference to related issues.
  • @mentions of the person or team responsible for reviewing proposed changes.
  • This pull request has a descriptive title.
  • Code is written according to the guidelines.
  • The checks by MISS_HIT style checker and linter, below the pull request, are successful (green).
  • Documentation is available.
  • Add changes to the changelog file under section Unreleased.
  • Model runs successfully.
  • Ask a meinatainer to re-generate exe file if matlab codes are changed. About how to create an exe file, see exe readme.

@SarahAlidoost SarahAlidoost marked this pull request as ready for review July 31, 2023 15:12
Copy link
Contributor

@BSchilperoort BSchilperoort left a comment

Choose a reason for hiding this comment

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

Looks good, nice work! I checked the model results and there seems to be no change at all between main and this branch.

It would be nice to have docstrings in many of the new functions though (what does the function do? what are the inputs? what's the source of the equations?). But I know you can't write those. Perhaps keeping track of the functions that still need a docstring in an issue could be a good idea?

@SarahAlidoost
Copy link
Member Author

Looks good, nice work! I checked the model results and there seems to be no change at all between main and this branch.

It would be nice to have docstrings in many of the new functions though (what does the function do? what are the inputs? what's the source of the equations?). But I know you can't write those. Perhaps keeping track of the functions that still need a docstring in an issue could be a good idea?

thanks a lot for reviewing and running the code. I agree that the code needs more documentation, I submitted issue #191 for this.

@SarahAlidoost
Copy link
Member Author

SarahAlidoost commented Aug 7, 2023

❗ 🔴 Waiting for addressing issues mentioned here before the merge.

@SarahAlidoost SarahAlidoost merged commit 51a0056 into main Sep 1, 2023
1 check passed
@SarahAlidoost SarahAlidoost deleted the fix_issue_181 branch September 1, 2023 09:20
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.

Refactor and move all cond*_ functions
2 participants