You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks to @terben for this suggestion. Maybe sewpy does not necessarily have to be able to read any format and return it as an astropy table, but it should at least be possible to have SExtractor write any of the SExtractor catalog formats to disk. I also wonder if we want to keep enforcing the filepath of the output catalog. Maybe the "config" should be able to overwrite the sewpy standard about this.
The text was updated successfully, but these errors were encountered:
Hi, I just start to use SEWPY, and it is already very helpful! Thanks!
I also agree that SEWPY should allow SExtractor to generate different format for catalog. Another reason is for the application of PSFEx, one has to choose VIGNET(X,Y) as output parameter, and has to use the FITS_LDAC format for catalog.
It would be very useful that SEWPY can just use the CATALOG_NAME and CATALOG_TYPE from the config, and only read it when the format is ASCII_HEAD.
Hi @dr-guangtou, thanks for the feedback!
Good point about the PSFEx application. We have this in mind as well, and should really implement all the current issues soon. We should also add better demos.
Thanks to @terben for this suggestion. Maybe sewpy does not necessarily have to be able to read any format and return it as an astropy table, but it should at least be possible to have SExtractor write any of the SExtractor catalog formats to disk. I also wonder if we want to keep enforcing the filepath of the output catalog. Maybe the "config" should be able to overwrite the sewpy standard about this.
The text was updated successfully, but these errors were encountered: