Closed jpinedaf closed 8 years ago
any ideas @keflavich @low-sky @rfriesen ?
I also see the problem in numpy 1.9.3
No immediate idea; there's nothing obvious in the numpy release notes unless it's this:
gh-3712: fix LAPACK error handling in lapack_litemodule
which came in numpy 1.7.2.
Are you running this on your machine or the GBT machines? I'm wondering if it has something to do with how numpy was compiled. The error suggests that the python code is using the wrong call specification (too many arguments or the wrong arguments) for a C function.
I'm running it on the GBT machines... but we are using the conda distribution
OK, I managed to track down the issue to a dump that is filled with NaNs... at this point I'm thinking of adding a check to make sure we have data like this (https://github.com/GBTAmmoniaSurvey/GAS/blob/master/GAS/gridregion.py#L214),
if doBaseline & np.sum(np.isfinite(specData)):
specData = baselineSpectrum(specData,order=1,
baselineIndex=baselineIndex)
Although this is not elegant and efficient... suggestions for a better implementation? I'll check this to confirm if solves the issue
Use np.all(np.isfinite(...))
or np.any(np.isnan(...)
.
You should probably raise an Exception or a loud warning if all-nan scans are encountered: those are bad and not expected, right?
The pipeline is running again. However, there is no warning implemented, since we don't have such a counter in the loop. At this moment we require that no NaNs should be present in the data, although I'm not sure if it is possible to have a single bad channel in the spectrum.
I tried to run the imager for L1455, but it fails at working with the first file already. This is something that has not changed from previous implementations, so I don't understand what changed... except the version of numpy that we are using (1.10.4)