INCATools / INCATools/boomer

"No possible resolution of perplexity" + no results

Open
#399 11 comments 0 reactions 0 assignees View on GitHub
Dominant language
Scala
Stars
37
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Hi,

I have been using boomer for some ontology merging tests and sometimes I get a "No possible resolution of perplexity" message. Then boomer stops without producing any result.

What does it mean exactly and how to solve the issue ?

I am using the binary "boomer-0.2" version.

I have attached the input ptable and ontology (that contains the two ontologies that I try to merge) that leads to this issue.

The ontologies merged are the VIDO (Virus Infectious Disease Ontology) and the IDO (Infectious Disease Ontology).

The ptable file is an arbitrary probabilistic reinterpretation of an alignment generated with LOGMAP (I have converted the logmap mappings into a ptable).

I have also attached the prefixes.yaml file.

This is my command line (launched on Windows 11) :
> boomer --ptable logmap-mappings-converted-to-ptable.tsv --ontology union-ido-vido-owl-functional-syntax.ofn --window-count 1 --runs 100 --prefixes prefixes.yaml --output boomer_output

Thanks for helping
[_BOOMER-INPUT-DATA.zip](https://github.com/INCATools/boomer/files/13921522/_BOOMER-INPUT-DATA.zip)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the Windows command with the attached _BOOMER-INPUT-DATA.zip, including the ptable, ontology, and prefixes.yaml files. Trace where “No possible resolution of perplexity” is emitted and determine why no output is produced; done means the cause is understood and the command either completes with results or reports the failure clearly.

Written by the indexing model from the issue text.

Assessment

Tech stack
scala
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.