Hi all,
I have submitted a small extension to the ExtensionsIndex and would appreciate a review when someone has a moment: Add SlicerMicroView extension by falkwiegmann · Pull Request #2390 · Slicer/ExtensionsIndex · GitHub
What it does
SlicerMicroView adds a reader and writer for VFF files, the native volume format of GE eXplore micro-CT scanners and of the MicroView software. VFF files then open directly through Add Data, and volumes can be exported back to VFF for MicroView.
The existing VFF reader in SlicerRT is written for radiotherapy dose files and does not handle scanner output: it requires header fields GE does not write, reads all voxels as float, and ignores the elementsize field that carries the real voxel size. The new reader follows MicroView’s own conventions, which I checked against the MicroView source: voxel size = spacing × elementsize, origin in voxel units, big-endian 16-bit data, values loaded as stored. Scanner calibration fields (water, air, boneHU) are kept as node attributes and written back on export.
Repository: GitHub - UBC-Ford-lab/SlicerMicroView: 3D Slicer extension to read and write GE eXplore / MicroView micro-CT volumes (VFF format). · GitHub (MIT)
screenshot (https://raw.githubusercontent.com/UBC-Ford-lab/SlicerMicroView/main/Screenshots/1.png)
Testing
- Python-only scripted module, no build dependencies.
- Self-test with synthetic files covers the GE header, minimal headers, endianness, writer round trips and the loading options.
- Tested on macOS with Slicer 5.12.3 on 1.4 GB and 2.1 GB GE eXplore CT 120 reconstructions and on scanner-side output; read-write-read round trips are byte-identical.
Happy to make any changes the reviewers would like.
Falk Wiegmann
Ford Lab, University of British Columbia