OpenwaterHealth / OpenwaterHealth/openlifu-python

Implement the virtual fitting optimization metric

Open
#148 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
27
Forks
21
Avg merge
1d 20m
Merged PRs (30d)
6

Description

This issue follows https://github.com/OpenwaterHealth/OpenLIFU-python/issues/147, where only the minimal grid search approach is developed.

More specifically, we want to have a better definition for what a good position is:

  1. Ray trace between each element and the target
    a. Get the material properties along the ray (checking only for sinus/non sinus region is sufficient, but we can also use a fully segmented head)
    b. Determine if the element is blocked
  2. Calculate the number of blocked elements

Once the steering and number of blocked elements has been determined for each position, candidate positions whose steering is outside the valid steering range for the probe are excluded, and then the remaining points are filtered to those with the lowest decile of blocked elements. From those final candidates, the “optimized” position is then chosen as the one closest to the target.

Contributor guide

Open the contributing guide

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 reviewing issue #147, which this work follows, and identify where the minimal grid search is implemented. Define how ray tracing, material checks, blocked-element counts, steering-range filtering, lowest-decile filtering, and target-distance selection fit together. Done means candidate positions are ranked by this optimization metric, but no files or tests are named in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
computer-graphics
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.