PEtab-dev / PEtab-dev/petab_select

Handle termination criteria for switching methods

Open
#35 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
14
Forks
1
PR merge metrics
No merged PRs in 30d

Description

FAMoS can start with forward, which may return 0 candidates if there are no feasible forward moves. In a normal forward search, this would reasonably end the search. However, since FAMoS can switch, the search should continue, but with a different method. A user observed that FAMoS does not continue, and instead the search is ended unreasonably early.

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 tracing FAMoS method switching and the termination handling for a forward search that returns zero candidates. Reproduce the reported case and check whether another method is available to continue. Done means the search does not end early when switching methods is still possible, while a normal forward search still terminates appropriately.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.