STIR swig MATLAB interface problems
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 160
- Forks
- 113
- Avg merge
- 12d 15h
- Merged PRs (30d)
- 1
Description
Both @robbietuk and I are having an issue with the MATLAB interface. The .m files try to call an unknown function stirMEX, whereas it should be stirMATLAB_wrap. A temporary, dirty fix was to symlink the mex file:
ln -s stirMATLAB_wrap.mexmaci64 stirMEX.mexmaci64
@robbietuk is using R2018b and I am using R2016b.
Contributor 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.
Research direction
Inspect the MATLAB .m files and the generated stirMATLAB_wrap mex file referenced in the report. Reproduce the interface call on a supported MATLAB version, then verify that the files use the available function name without requiring the temporary stirMEX symlink.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- matlab
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100