SourceXtractorPlusPlus
SourceXtractorPlusPlus copied to clipboard
astrorama
SourceXtractor++, the next generation SExtractor
When fitting a bulge+disk model to VIS coadded data the comparison between auto_mag (== TU mags) and the fitted mags looks like this:  The PSF is a bit naive...
I ran some Euclid test data with single image fitting (3 bands, ~4 images per band per pixels) using different number of cores to test the scaling of the multi-threading....
Dear SE++ developers, thanks for all the hard work. I have a question, is SE++ able to use CHI2 detection images produced by Swarp? In 'sextractor classic' these images were...
It seems that SourceXtractorPlusPlus is able to use an external header (.head) file, for instance to apply the distortion terms (PVi_i): is that correct ? If I am not mistaken,...
The output-properties _AperturePhotometry_ and _AutoPhotometry_ are treated differently: * _AperturePhotometry_ is **only** applied to the measurement image(s). In case that the _AperturePhotometry_ of the detection image is wanted, a python...
Hello, as we are using the model-fitting options of this software to do disk+bulge decomposition of galaxies, we usually fit multiple models to one image. Currently the check-image-model-fitting returns one...
It turns out that the flux initialization has quite an influence on the photometric result when running SE++ on mulit-band data. As an example I am using a simulated dataset...
Sorry, I think we did not reach a conclusion last week, did we? Personally, I vote for @marcschefer's proposal of clipping. Perhaps with a warning logged into the terminal. @mkuemmel,...
Hello, I am running sourcextractor++ on some simulations using FlexibleModelFitting and a constant psf (I have tried both fits file and psf-fwhm and psf-pixel-sampling values ). I am getting for...
I ran SE++ with sersic fitting on simulated images with sersic profile (in the context of the Euclid Morphology Challenge). When plotting the difference between two SE++ parameters pixel_centroid_x/y and...