Closed timj closed 9 years ago
The reason SExtractor hasn't been updated is because of the need for more external dependencies. The main issue being ATLAS. Normally we'd import a version of this into thirdparty, but the ATLAS build system is specialised for optimisations, rather than portability, so is quite problematic.
The two versions are just the native one and the EXTRACTOR fork. The EXTRACTOR fork uses the NDF library and AST WCS.
It turns out that the dependency on ATLAS can be removed by configuration options, so that issue can be worked around and I've updated the SExtractor and EXTRACTOR code bases. @talister try this out and let me know if this all works as expected.
This upgrade has happened in 87f488267c11634e15431d7053edfc3f56d72064 and 744ae3723db8d1ce89888c0f46efeb11c7c7663f so closing for now.
SExtractor is currently at v2.5-1. @talister would like SExtractor to be upgraded to V2.19.5, particularly as this would allow catalogues to be created in a form that would allow us to compare autoastrom with scamp.
@pwdraper It's not at all clear to me how to do the SExtractor merge with upstream as there seem to be two SExtractor submodules and I'm confused as to the distinction and which files are really needed to provide NDF support. Can you please give me some guidance?