Don't require ".fits" extension

[dstndstn]

I just encountered:

processFile.py fpC-004192-r4-0300.fit --output output --clobber-config -c gain=2 doVariance=True calibrate.astrometry.solver.matchThreshold=14. calibrate.astrometry.solver.maxStars=100
: Loading config overrride file '/nfs/lsst/home/dstn/lsst/obs_file/config/processFile.py'
: Loading config overrride file '/nfs/lsst/home/dstn/lsst/obs_file/config/processFile.py'
: input=/nfs/lsst/home/dstn/lsst/lsst_dm_stack_demo-8.0.0.0
: output=/nfs/lsst/home/dstn/lsst/lsst_dm_stack_demo-8.0.0.0/output
CameraMapper: Loading registry registry from /nfs/lsst/home/dstn/lsst/lsst_dm_stack_demo-8.0.0.0/output/_parent/registry.sqlite3
 WARNING: No data found for dataId=OrderedDict([('calexp', 'fpC-004192-r4-0300')])

and the solution is:

> mv fpC-004192-r4-0300.fit fpC-004192-r4-0300.fitsmv: cannot stat `fpC-004192-r4-0300.fit': No such file or directory
> processFile.py fpC-004192-r4-0300.fits --output output --clobber-config -c gain=2 doVariance=True calibrate.astrometry.solver.matchThreshold=14. calibrate.astrometry.solver.maxStars=100
: Loading config overrride file '/nfs/lsst/home/dstn/lsst/obs_file/config/processFile.py'
: Loading config overrride file '/nfs/lsst/home/dstn/lsst/obs_file/config/processFile.py'
: input=/nfs/lsst/home/dstn/lsst/lsst_dm_stack_demo-8.0.0.0
: output=/nfs/lsst/home/dstn/lsst/lsst_dm_stack_demo-8.0.0.0/output
CameraMapper: Loading registry registry from /nfs/lsst/home/dstn/lsst/lsst_dm_stack_demo-8.0.0.0/output/_parent/registry.sqlite3
processFile: Processing {'calexp': 'fpC-004192-r4-0300'}

If processFile's argument is a file that exists, why require its filename to be .fits? Depending on filename extensions is a Windows-y ickfest.

[RobertLuptonTheGood]

There's a ticket on that somewhere.

It's a "feature" of the butler's glob matching, and will go away with the new butler when KT finds some time...

                    R