[gnuastro-commits] master f44894d: Library (reading WCS): removed warning for unreasonable LONPOLE

[Mohammad Akhlaghi]

branch: master
commit f44894d8ee4248ac9d69756235c6ea67c10118a9
Author: Mohammad Akhlaghi <address@hidden>
Commit: Mohammad Akhlaghi <address@hidden>

    Library (reading WCS): removed warning for unreasonable LONPOLE
    
    In the previous commit, an extra warning was added to report unreasonable
    LONPOLE values. But this was wrong: when its not defined it always gets an
    absurd value (even when there isn't any PV matrix!), and default value is
    written for it automatically.
    
    With this commit, the warning has been removed.
---
 lib/wcs.c | 14 --------------
 1 file changed, 14 deletions(-)

diff --git a/lib/wcs.c b/lib/wcs.c
index 3074e48..0d4a798 100644
--- a/lib/wcs.c
+++ b/lib/wcs.c
@@ -190,20 +190,6 @@ gal_wcs_read_fitsptr(fitsfile *fptr, size_t hstartwcs, 
size_t hendwcs,
           printf("latpole: %f\n", wcs->latpole);
           */
 
-          /* When LONPOLE isn't given and the PV matrix information is not
-             given properly, `wcs->lonpole' can have absurd values (on the
-             order of 1e50 or something). In such cases, we can have this
-             WCSLIB error: "wcsset ERROR 5: Invalid parameter value.". To
-             avoid confusion for the users in such cases, we'll see if the
-             value is in the reasonable range and if not, we'll inform the
-             user.*/
-          if(wcs->lonpole>360 || wcs->lonpole<-360)
-            fprintf(stderr, "WARNING: the inferred `lonpole' of the input's "
-                    "WCS is not reasonable (with a value of `%f').\n\n"
-                    "If `LONPOLE' isn't in the FITS keywords, this is "
-                    "probably because of the `PV%%_1' keyword(s).\n\n",
-                    wcs->lonpole);
-
           /* Set the WCS structure. */
           status=wcsset(wcs);
           if(status)