Issues with BPP and cosmetic correction

[dwood]

I just updated to the latest of P/I for Mac OS 10.9 and keep getting the following error when I run the BPP script:

PCL FITS Format Support: Unable to open FITS file:
/Users/Daves/Desktop/5907 pixi/calibrated/light/cosmetized/ NGC 5907 Light.00000687_c_cc.fit
CFITSIO error message stack:
01 : failed to find or open the following file: (ffopen)
02 : /Users/Daves/Desktop/5907 pixi/calibrated/light/cosmetized/ NGC 5907 Light.00000
03 : 687_c_cc.fit

The file does exist and I can manually open the file without issus.  I can also uncheck the the apply cosmetic correction box under Light frames and the script will runt to completion. 

Any ideas as to what may be causing the script to crash?

Thanks

Dave

[pfile]

i will guess that it's all the spaces in the filename, and in particular the leading space in the name. try replacing all the spaces with underscores and see what happens.

rob

[dwood]

The file naming convention is what is created by the BPP script.  I check the file that lives in the "cosmetized" folder as created by the BPP script and they are the same. 

 

Dave

[dwood]

i will guess that it's all the spaces in the filename, and in particular the leading space in the name. try replacing all the spaces with underscores and see what happens.

rob

Ok I see what you're referring to - interesting I've been using the same file naming convention for several years and never had the script crash like this.

Dave

[dwood]

i will guess that it's all the spaces in the filename, and in particular the leading space in the name. try replacing all the spaces with underscores and see what happens.

rob

Thanks -- it turns out it was the space in the front of the file name.  Doh....

[pfile]

cool, yeah this is i guess a linux vs. windows/macos thing. generally in linux the space character is a file delimiter and so filenames need to be quoted or the spaces "escaped" to make sure a filename with spaces is treated as a single filename and not two separate "things".

probably the script has a place where it's not expecting a space at the beginning of a filename...

rob