Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Regeression for Table dtype between 4.0.1 and 4.0.2

See original GitHub issue

In [1]: import numpy as np

In [2]: from astropy.table import Table

In [3]: URL = "https://github.com/astroML/astroML-data/raw/master/datasets/sgSDSSimagingSample.fit.gz"

In [4]: data = Table.read(URL)
Downloading https://github.com/astroML/astroML-data/raw/master/datasets/sgSDSSimagingSample.fit.gz
|===========================================================================================================|  23M/ 23M (100.00%)         0s

In[5]: data.dtype
Out[5]: dtype([('ra', '>f8'), ('dec', '>f8'), ('run', '>i2'), ('rExtSFD', '>f8'), ('uRaw', '>f8'), ('gRaw', '>f8'), ('rRaw', '>f8'), ('iRaw', '>f8'), ('zRaw', '>f8'), ('uErr', '>f8'), ('gErr', '>f8'), ('rErr', '>f8'), ('iErr', '>f8'), ('zErr', '>f8'), ('uRawPSF', '>f8'), ('gRawPSF', '>f8'), ('rRawPSF', '>f8'), ('iRawPSF', '>f8'), ('zRawPSF', '>f8'), ('upsfErr', '>f8'), ('gpsfErr', '>f8'), ('rpsfErr', '>f8'), ('ipsfErr', '>f8'), ('zpsfErr', '>f8'), ('type', '>i2'), ('ISOLATED', '>i4')])

While with 4.0.2+, I get

dtype([('ra', '>f8', (1,)), ('dec', '>f8', (1,)), ('run', '>i2', (1,)), ('rExtSFD', '>f8', (1,)), ('uRaw', '>f8', (1,)), ('gRaw', '>f8', (1,)), ('rRaw', '>f8', (1,)), ('iRaw', '>f8', (1,)), ('zRaw', '>f8', (1,)), ('uErr', '>f8', (1,)), ('gErr', '>f8', (1,)), ('rErr', '>f8', (1,)), ('iErr', '>f8', (1,)), ('zErr', '>f8', (1,)), ('uRawPSF', '>f8', (1,)), ('gRawPSF', '>f8', (1,)), ('rRawPSF', '>f8', (1,)), ('iRawPSF', '>f8', (1,)), ('zRawPSF', '>f8', (1,)), ('upsfErr', '>f8', (1,)), ('gpsfErr', '>f8', (1,)), ('rpsfErr', '>f8', (1,)), ('ipsfErr', '>f8', (1,)), ('zpsfErr', '>f8', (1,)), ('type', '>i2', (1,)), ('ISOLATED', '>i4', (1,))])

I assume this is a bug as a change like this should not happen in LTS.

This regression triggered multiple user bug reports downstream in astroML: https://github.com/astroML/astroML/issues/232

Issue Analytics

State:
Created 3 years ago
Comments:11 (11 by maintainers)

Top GitHub Comments

3reactions

bsipoczcommented, Feb 24, 2021

@bsipocz - can you fix that FITS file on the astroML site to remove the TDIMn = ‘(1)’ headers?

Yes, that will in fact work, and will be totally transparent for users. Thanks!

0reactions

taldcroftcommented, Feb 25, 2021

I’m closing, and @bsipocz or others can re-open if desired.

Top Results From Across the Web

Input contains infinity or a value too large for dtype('float64').

This tutorial explains how to fix the following error in Python: Input contains NaN, infinity or a value too large for dtype('float64').

Essential Basic Functionality — pandas 0.19.2 documentation

iterrows() : Iterate over the rows of a DataFrame as (index, Series) pairs. This converts the rows to Series objects, which can change...

BUG: 1.3.0 DataFrame.agg over categorical columns with non ...

When a aggregation of the rows is run on a dataframe with categorical columns and non-unique indices, the result is the wrong length....

Logistic Regression Classifier Tutorial - Kaggle

I build a Logistic Regression classifier to predict whether or not it will rain tomorrow in Australia. I train a binary classification model...

`Pandas data cast to numpy dtype of object. Check input data ...

I faced this issue reviewing StatLearning book lab on linear regression for the "Carseats" dataset from statsmodels, where the columns 'ShelveLoc', ...