SimVascular / SimVascular/vascularmodel

0116_H_PULM_ALGS has a model creation error

Open
#34 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
HTML
Stars
5
Forks
6
PR merge metrics
No merged PRs in 30d

Description

Description

Moving on to the next Alagille model 0116_H_PULM_ALGS, we are faced with a "[GetSingleLoop] An error occurred processing cell 2" warning while trying to create the model from the segmentations.

Tracing back to https://github.com/SimVascular/SimVascular/issues/1154 I discovered the following: "The PolyDataException exception object returns the triangle where the computation goes into an infinite loop. This is then displayed in red. The user can then loft the segmentations used in the union to get an idea what the problem is and possibly modify the segmentations a bit to fix it."

Posting this issue to start my investigation and logging of findings.

Reproduction

Launch SimVascular 2025.12.21 from Ubuntu 24 computer and try to build a model from the segmentations.

Expected behavior

Create a nice model from the segmentations.

Additional context

No response

Code of Conduct
  • I agree to follow this project's Code of Conduct and Contributing Guidelines

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

Reproduce the model-building failure in SimVascular 2025.12.21 on Ubuntu 24 and capture the “GetSingleLoop” warning for cell 2. Read issue #1154 for the PolyDataException guidance, then document what the investigation reveals about the 0116_H_PULM_ALGS segmentations and the model-creation error.

Written by the indexing model from the issue text.

Assessment

Tech stack
ubuntu
Domain
computer-graphics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.