Bingo NoSQL Substructure matcher does not implement `currentSimValue`
- Dominant language
- C++
- Stars
- 406
- Forks
- 134
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 24
Description
**Steps to Reproduce**
I'm doing a parallel substructure search (across a large corpus split into several individual bingo dbs).
Python 3.x, epam.indigo==1.14.0
```
m = loadQueryMolecule(...)
matcher = db.searchSub(m)
if matcher.next():
id = matcher.getCurrentId()
sim_score = matcher.getCurrentSimilarityValue()
```
**Expected behavior**
Some measure of relevancy should be provided in the score in order to be able to properly sort the results. Sorting by order emitted is not an option since the results must be merged with other result sets.
**Actual behavior**
A "not implemented" error is raised.
**Indigo/Bingo version**
epam.indigo==1.14.0
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the Python example using Bingo NoSQL `searchSub`, `getCurrentId`, and `getCurrentSimilarityValue`, then trace the corresponding implementation for `currentSimValue`. Done means parallel substructure searches return a usable similarity score instead of a “not implemented” error, allowing result sets to be sorted and merged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- databases, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100