Can you post your job file here so we can take a look?
An alternative that should work out is to manually convert the DICOM data to NIfTI with SPM, dcm2niix or (my recommendation) dicm2nii which is actually included in the Osprey libraries. You can then supply the NIfTI files in the job file instead of pointing to the DICOM folder. The conversion is a useful step that you will likely do eventually anyway.
Thanks for the report. I’ve pushed a change to the develop branch in the Osprey GitHub repository. Please pull the latest changes from there and try again with the job file changed as described below:
The strrep(which( bits in the job files is really only there to make sure that the example data in the GitHub repository work out of the box for everyone; however, they seem to really confuse people more than help. I should look into finding a better way to solve this.