Are the "repaired CDs" printed as feedback in `SelectValidCd` guaranteed to be object-inhabited?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start by locating SelectValidCd and tracing how valid CDs and repaired CDs are generated and displayed. Check whether the repaired CDs always admit object diagrams satisfying objectProperties, using task instances or tests if available. Done means establishing whether a counterexample exists and, if it does, identifying what needs to change so CDs shown as valid permit such object diagrams.
Written by the indexing model from the issue text.
Description
Concerning question from https://github.com/fmidue/modelling-tasks/issues/701#issuecomment-6469693402,
For
SelectValidCd, valid CDs as a solution stores corresponding ODs, but the valid CDs after repairing errors in those invalid CDs are not guaranteed to have corresponding ODs satisfyingobjectProperties, because they only store changes of repairing. It might affect the feedback a bit, because the repaired CD might not have corresponding ODs satisfyingobjectProperties.
I do think it would be nice if CDs claimed/displayed as valid indeed permit ODs. Have you seen an example in that task type (an instance of it) where actually one of the CDs claimed as valid does not have ODs? It could in theory be the case that somehow by the existing generation/repair strategy it never happens that the thus obtained CDs have no ODs. Maybe by some argument that they are related to a known-good (including the existence of ODs) CD in a particular way (maybe only removing some relationships between classes, and some meta-argument that removing relationships can never make an inhabited CD un-inhabitable or so).
Originally posted by @jvoigtlaender in https://github.com/fmidue/modelling-tasks/issues/703#issuecomment-6482213009
- Dominant language
- Haskell
- Stars
- 0
- Forks
- 3
- Avg merge
- 19h 37m
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fmidue/modelling-tasks
-
bug cd-od testing
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
fmidue/modelling-tasks#508 · 4 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
fmidue/modelling-tasks#706 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
fmidue/modelling-tasks#692 ·
-
Find new configOpen
Difficulty 3/5 1-2 days Newbie friendliness 45/100
fmidue/modelling-tasks#688 · 1 comment ·
-
Cleanup / remove dead codePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
fmidue/modelling-tasks#687 ·
All issues in fmidue/modelling-tasks
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
yesodweb/wai#1163 · 1 reaction ·
Maintainers usually reply within 1 day
-
Web.Scotty.Trans.Lazy.setHeader calls addHeader instead of setHeaderPossibly taken @tusharad claimed this 2 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
scotty-web/scotty#436 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
input-output-hk/haskell.nix#2617 ·
-
easy first-contributor first-contributors good first issue haskell help wanted up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 82/100
fork-commit-merge/fork-commit-merge#8455 ·
Maintainers usually reply within 1 day
-
new tool
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
dense-analysis/ale#5176 ·