getannotation({"annotations":[{"id":5610,"username":"seb","context":"vizierTable","element":"J/ApJ/835/223","creationDate":1548089151000,"parentId":5589,"isAdmin":"true","isPrivate":"false","text":"Hello,\r\nI tried downloading this FITS file and opening it with various tools.\r\nIt looks like a potential bug of the FITS viewer tool, and not an error in the data file itself. For example, fv is not interpreting correctly the header information. If you open the same FITS file with TOPCAT, the two column values are correct.\r\n\r\nThe FITS standard [link url\u003dhttps://fits.gsfc.nasa.gov/standard40/fits_standard40aa-le.pdf](see p.20)[/link] states that \"It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword\". So the following description, even if not recommended, is not forbidden :\r\n\r\nTTYPE18 \u003d 'b_logMBH'           / [1/10]? Lower limit of logMBH                  \r\n          \r\nTTYPE19 \u003d 'B_logMBH'           / [3/11]? Upper limit of logMBH                  \r\n\r\nTOPCAT interprets correctly the two columns and their values.\r\nfv is treating them case-insensitive, and duplicates values of column 18 into column 19.\r\nMost likely a bug to report to fv developers.","parsedText":"Hello,\u003cbr /\u003eI tried downloading this FITS file and opening it with various tools.\u003cbr /\u003eIt looks like a potential bug of the FITS viewer tool, and not an error in the data file itself. For example, fv is not interpreting correctly the header information. If you open the same FITS file with TOPCAT, the two column values are correct.\u003cbr /\u003e\u003cbr /\u003eThe FITS standard \u003ca href\u003d'https://fits.gsfc.nasa.gov/standard40/fits_standard40aa-le.pdf' rel\u003d'nofollow'\u003e(see p.20)\u003c/a\u003e states that \u0026quot;It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword\u0026quot;. So the following description, even if not recommended, is not forbidden :\u003cbr /\u003e\u003cbr /\u003eTTYPE18 \u003d 'b_logMBH'           / [1/10]? Lower limit of logMBH                  \u003cbr /\u003e          \u003cbr /\u003eTTYPE19 \u003d 'B_logMBH'           / [3/11]? Upper limit of logMBH                  \u003cbr /\u003e\u003cbr /\u003eTOPCAT interprets correctly the two columns and their values.\u003cbr /\u003efv is treating them case-insensitive, and duplicates values of column 18 into column 19.\u003cbr /\u003eMost likely a bug to report to fv developers.","adminText":"","type":"comment"},{"id":5589,"username":"niu541412","context":"vizierTable","element":"J/ApJ/835/223","creationDate":1547837352000,"parentId":-1,"isAdmin":"false","isPrivate":"false","text":"The fits files of this paper which can are downloaded directlly from the ftp tab(http://cdsarc.u-strasbg.fr/viz-bin/cat/J/ApJ/835/223#browse) have duplicated columns. For [link url\u003dhttp://cdsarc.u-strasbg.fr/viz-bin/nph-Cat/fits?J/ApJ/835/223/table1.dat]fits 1[/link], two columns named [b]B_logMBH [/b]and [b]b_logMBH[/b] have the same value. Actually, they should be the upper and lower limit values of the blackhole mass. In fits 2, a similar problem of NH exists. Dat file and html files are correct.","parsedText":"The fits files of this paper which can are downloaded directlly from the ftp tab(http://cdsarc.u-strasbg.fr/viz-bin/cat/J/ApJ/835/223#browse) have duplicated columns. For \u003ca href\u003d'http://cdsarc.u-strasbg.fr/viz-bin/nph-Cat/fits?J/ApJ/835/223/table1.dat' rel\u003d'nofollow'\u003efits 1\u003c/a\u003e, two columns named \u003cb\u003eB_logMBH \u003c/b\u003eand \u003cb\u003eb_logMBH\u003c/b\u003e have the same value. Actually, they should be the upper and lower limit values of the blackhole mass. In fits 2, a similar problem of NH exists. Dat file and html files are correct.","adminText":"","type":"errorNotification","status":"pending"}],"requestedCatalogue":"J/ApJ/835/223"})