> *Error*: no key to print in table OBJECTS

[wtgee]

I'm posting this here because the forums have 26,000 views on the comment and yet you only loosely refer to having fixed the problem without actually ever stating how to fix the problem. This issue is now over 5 years old.

[wtgee]

For anyone else looking, you must uncomment some of the column headers in the default.param or pass them on the command line. The manual refers to these being optional, but you get the error if you don't specify any.

[SashaBrownsberger]

I encountered this error again on 09/27/2018 with an installation of sextractor version 2.19.5 on a 2010 macbook pro running Yosemite. I managed to fix the error using the method described above by wtgee.

More specifically, I opened up the provided default.param file (in the sextractor-2.19.5/config/ directory), which came with every row commented out (meaning a # proceeds every line). I just opened up default.param with vi ($ vi default.param) and deleted the # on the first line (for me, that was: #NUMBER Running object number).

sextractor now completes successfully, though I have yet to test it beyond running the sex command on a single fits file.

[qruiwu]

I encountered this error again on 09/27/2018 with an installation of sextractor version 2.19.5 on a 2010 macbook pro running Yosemite. I managed to fix the error using the method described above by wtgee.

More specifically, I opened up the provided default.param file (in the sextractor-2.19.5/config/ directory), which came with every row commented out (meaning a # proceeds every line). I just opened up default.param with vi ($ vi default.param) and deleted the # on the first line (for me, that was: #NUMBER Running object number).

sextractor now completes successfully, though I have yet to test it beyond running the sex command on a single fits file.

That‘s really helpful！