owlcollab / owlcollab/owltools

FastOwlSim's SimGIC scoring discrepancy

Open
#187 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
115
Forks
34
PR merge metrics
No merged PRs in 30d

Description

SimGIC score calculated using FastOwlSim doesn't match among output files written in FORMATTED and CSV formats. However, SimGIC calculated using SimpleOwlSim matches with that calculated using FastOwlSim in output format FORMATTED.

Input owl file: simont.owl
Properties file: properties.txt
General command used: owltools simont.owl --fsim-basic -p properties.txt -o out.txt

  1. Using fsim-basic and output format as CSV: out-fsim-basic_csv.txt
  2. Using fsim-basic and output format as FORMATTED: out-fsim-basic_formatted.txt
  3. Using sim-basic and output format as CSV: out-sim-basic_csv.txt

In both above csv files, I assume values in the last column as SimGIC scores (column titles don't align with those values, or else column title was missing).

Why do scores differ depending on file format? Besides presumed code refactoring, is there any difference between scoring methodology used in FastOwlSim and SimpleOwlSim?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the reported owltools simont.owl --fsim-basic -p properties.txt -o out.txt command with the linked simont.owl and properties.txt inputs. Compare the CSV and FORMATTED outputs, including their column headings and final values, with the provided reference files; done means the output formats agree on SimGIC scores and any remaining FastOwlSim/SimpleOwlSim difference is explained or corrected.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.