-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve PreProcessing workflow to support BVR cfg generation #131
Comments
For us, the most useful UI to generate a config file would have inputs controls to identify Calibration, Radiograph, and Volume subdirectories, Optimization Offsets (already present), Volume Flip (already present), Render Resolution (2 number input boxes), and Voxel Size (3 number input boxes). Calibration files, folders containing radiographs, and volume files would be parsed from the subdirectories (this assumes that calibration files and radiograph image folders have a camera identifier in their filename). The information from the input controls would be compiled into a .cfg file (Version 1.1). For reference, here is the current Generate Config tab: |
The advanced Options tab may be modified to meet some of these needs along with a more comprehensive Generate Config drop down For reference, the folder explorer to the right shows the subdirectories typically found within the RadiographImages folder and the maycam files found in Calibration folder. (John - could you please add a screen shot from your projects too?) Trial Name in General Input tab currently is a manual fill in... options for batch generation.. can't make too many file structure or naming restricitons |
That makes sense. A few more questions, to clarify:
Do we want to automatically load all volume files found in the specified volume subdirectory? Should we assume that the volume flip and voxel size properties are set once and they apply to all volumes files found?
Matching up the radiographs to their camera calibration files might be difficult in general if we don't require a certain name format/convention or if we don't tell SAM what exact name to look for. What are your thoughts on this? |
q1. Do we want to automatically load all volume files found in the specified volume subdirectory? q2.Should we assume that the volume flip and voxel size properties are set once and they apply to all volumes files found? |
@sbelsk suggest relocating trial name in the General Input ui drop down into the Generate Config group |
See https://autoscoper.readthedocs.io/en/latest/file-specifications/config.html
The text was updated successfully, but these errors were encountered: