Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Comparing a FITS file with one in a subdirectory

See original GitHub issue

I knew that when running fitsdiff to compare a file in the default directory with one of the same name in a subdirectory that it was necessary to explicitly give the name of the file in the subdirectory, but today I typed the following by mistake:

fitsdiff dms_230_491_refpix.fits today_prev/

and fitsdiff reported “No differences found.” However, I knew that the files did differ, so I ran fitsdiff again:

fitsdiff dms_230_491_refpix.fits today_prev/dms_230_491_refpix.fits

and fitsdiff showed several differences.

It’s probably relevant that there was only one file in today_prev/.

Issue Analytics

State:
Created 6 years ago
Comments:7 (6 by maintainers)

Top GitHub Comments

1reaction

drdavellacommented, Oct 17, 2017

It sounds like fitsdiff should make sure that all of the file arguments are real files (i.e. not directories).

0reactions

saimncommented, Jan 15, 2018

@sushobhana - Yes, the fix should be simple enough (and the issue is quite well described above, ask if you need more specific precision). It will also need unit tests, you may want to read the developer documentation to get a better understanding of the process. The is also an attempt in #6993 but it seems to be stalled.