astromatic / psfex Goto Github PK

Open the .xml file in the tutorial as follows

But I open the. xml file as follows，I cannot expand the corresponding tag to see the details.

From reading the documentation, I am not sure whether or not psfex has the capability to fit a single polynomial across chip gaps instead of completing an individual polynomial fit for each chip. To accomplish this, would I set NEWBASIS_TYPE=PCA_COMMON? Also, what is the difference between HIDDENMEF_TYPE and MEF_TYPE?

Hi! I have a fits file which contains my synthetic PSF model which I want to feed into SExtractor. Is there any code snippet available to convert this fits file into .psf format which is accepted by SExtractor?

http://www.astromatic.net/software/psfex says 3.17.1 is the latest version, but newer versions are in this github repository. Maybe update the latest version on the web site?

Dear all,

I am discovering this excellent software, and its good documentation (a really cool source of informations for me).

As there does not seem to be much opensource tool to analyse astro image quality on linux (like ccd inspector), I was impressed by the quality of this software.

I am definitely interested in testing it and using it. at some point, I also would like to implement proper python binding with Pybind11, if I have time.

Anyway, for now, I just wanted to report what I think is a small typo in the documentation:
https://psfex.readthedocs.io/en/latest/Installing.html

I think on ubuntu it is

sudo apt-get install psfex

instead of

apt-get psfex

It is not much, but I wanted to use this issue section to thank you for all the work

Hi I'm trying to build PSFex from source on a server.

The dependencies have all been installed from the RHEL repository. However, during the making phase I got an error

/bin/sh ../libtool --tag=CC --mode=link gcc -D_REENTRANT -g -O2 -o psfex catout.o check.o context.o cplot.o diagnostic.o fft.o field.o fitswcs.o homo.o main.o makeit.o misc.o pca.o prefs.o psf.o sample.o vignet.o xml.o ./fits/libfits.a ./levmar/liblevmar.a ./wcs/libwcs_c.a -L/usr/lib64/atlas -ltatlas -lfftw3f_threads -lfftw3f -lm -lplplot
libtool: link: gcc -D_REENTRANT -g -O2 -o psfex catout.o check.o context.o cplot.o diagnostic.o fft.o field.o fitswcs.o homo.o main.o makeit.o misc.o pca.o prefs.o psf.o sample.o vignet.o xml.o ./fits/libfits.a ./levmar/liblevmar.a ./wcs/libwcs_c.a -L/usr/lib64/atlas -ltatlas -lfftw3f_threads -lfftw3f -lm -lplplot
/usr/bin/ld: diagnostic.o: undefined reference to symbol 'pthread_join@@GLIBC_2.2.5'
//usr/lib64/libpthread.so.0: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status

I am not sure what is missing.

Cheers,

Bovornpratch

This warning appears when building 3.24.2:

catout.c:215:33: warning: 'memset' call operates on objects of type 'outsamplestruct' (aka 'struct outsample') while the size is based on a different type 'outsamplestruct *' (aka 'struct outsample *') [-Wsizeof-pointer-memaccess]
    memset(outsample, 0, sizeof(outsample));
           ~~~~~~~~~            ^~~~~~~~~
catout.c:215:33: note: did you mean to dereference the argument to 'sizeof' (and multiply it by the number of elements)?
    memset(outsample, 0, sizeof(outsample));
                                ^~~~~~~~~
1 warning generated.

Dear @ebertin,

Could you create a new release tag with the OpenBLAS support modifications? I am trying to create a Homebrew recipe for installing PSFex in mac, but without it, I would need to do patch outside this repo.

Thanks!

These warnings appear when building 3.24.2:

fitswrite.c:455:34: warning: address of array 'key->printf' will always evaluate to 'true' [-Wpointer-bool-conversion]
            fprintf(stream, key->printf?key->printf:"%d", (int)*ptr);
                            ~~~~~^~~~~~~
fitswrite.c:541:34: warning: address of array 'key->printf' will always evaluate to 'true' [-Wpointer-bool-conversion]
            fprintf(stream, key->printf?key->printf:"%d", (int)*ptr);
                            ~~~~~^~~~~~~
2 warnings generated.

When compiling on my Mac, I see:

Making all in levmar
gcc -DHAVE_CONFIG_H -I. -I../.. -D_REENTRANT -g -O2 -MT lmbc.o -MD -MP -MF .deps/lmbc.Tpo -c -o lmbc.o lmbc.c
In file included from lmbc.c:84:
./lmbc_core.c:324:13: error: implicitly declaring library function 'finite' with type 'int (double)' [-Werror,-Wimplicit-function-declaration]
if (!LM_FINITE(fpls)) {
^
./compiler.h:63:19: note: expanded from macro 'LM_FINITE'
#define LM_FINITE finite // ICC, GCC
^
./lmbc_core.c:324:13: note: include the header <math.h> or explicitly provide a declaration for 'finite'
./compiler.h:63:19: note: expanded from macro 'LM_FINITE'
#define LM_FINITE finite // ICC, GCC

Based on this thread:
igraph/igraph#1349

changing finite -> isfinite in compiler.h passes. Would this be safe to use on other systems?