https://github.com/UCBerkeleySETI/turbo_seti
Tip revision: 57d14a61e146cd2a035f64869ee8cb5e17d656a9 authored by Emilio Enriquez on 29 April 2019, 00:29:35 UTC
Bugfix, the internal data handling was assuming the frequency was in ascending order. This used to be the case in blimpy until it was changed in March 2nd 2018. This bug would cause the drift rate found by the code to have the opposite sign if the data is stored with the frequency in descending order.
Bugfix, the internal data handling was assuming the frequency was in ascending order. This used to be the case in blimpy until it was changed in March 2nd 2018. This bug would cause the drift rate found by the code to have the opposite sign if the data is stored with the frequency in descending order.
Tip revision: 57d14a6
| File | Mode | Size |
|---|---|---|
| turbo_seti | ||
| voyager_test | ||
| .gitignore | -rw-r--r-- | 34 bytes |
| .travis.yml | -rw-r--r-- | 651 bytes |
| Dockerfile | -rw-r--r-- | 1.5 KB |
| LICENSE | -rw-r--r-- | 1.0 KB |
| README.md | -rw-r--r-- | 4.0 KB |
| setup.py | -rw-r--r-- | 1.7 KB |
