Ligands not part of a thermodynamic cycle on perturbation mapping
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start with Lomap's perturbation-mapping behavior around the radial parameter and the gufe-provided 3D coordinates mentioned in the issue. Determine whether the requested change is enforcing thermodynamic cycles, addressing ligand alignment in scoring, or both, then define completion criteria before implementation.
Written by the indexing model from the issue text.
Description
While working with Lomap I noticed that some of the ligands in the perturbation mapping weren't part of a thermodynamic cycle, with only one edge connecting them to the rest of the network. I tried using the radial parameter but still observed the same.
Is there a way to force this behavior so that all ligands are part of a thermodynamic cycle?
I also noticed a slight misalignment between some of my ligands (3D coordinates). Could that play a role in the scoring from Lomap since they're obtained from gufe?
- Dominant language
- Python
- Stars
- 45
- Forks
- 15
- Avg merge
- 18h 11m
- Merged PRs (30d)
- 4
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 OpenFreeEnergy/Lomap
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
OpenFreeEnergy/Lomap#180 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
OpenFreeEnergy/Lomap#127 ·
-
Ring-related LOMAP rules: origin, behaviour and inconsistenciesPossibly taken @jthorton claimed this 17 days ago. Open
OpenFreeEnergy/Lomap#178 · 2 assignees ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
OpenFreeEnergy/Lomap#167 ·
-
Deprecate DBMoleculesMay be free again @IAlibay claimed this 156 days ago, and no pull request is open. Open
OpenFreeEnergy/Lomap#149 · 8 comments · 1 assignee ·
All issues in OpenFreeEnergy/Lomap
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
gorakhargosh/watchdog#1462 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
openwisp/openwisp-monitoring#889 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
roman-corgi/corgisim#327 ·
Maintainers usually reply within 2 days
-
agent:WSL bug code-review linux pri:medium sev:low tooling
Difficulty 2/5 Half a day Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
[Bug]: opencode_go chat route drops reasoning_effort (even 'none'), while the same endpoint honors it via custom_llm_provider=openaiPossibly taken @arvindkumar-ship-it claimed this today. Openllm translation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
BerriAI/litellm#51871 · 1 comment ·
Maintainers usually reply within 1 day