Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#250 Change limit on maximum magnitude error

Defect
closed-fixed
David Benn
Algorithms (37)
7
2011-03-01
2011-01-04
Sara Beck
No

While examining two SuperWASP files that have a maximum magnitude error which is smaller than 0.01 (which is a default we have used), I encountered the following error messages:

[while trying to read-in 1SWASP+J194815.46%2B430736.9.fits]
"New Star From Observation Source Read Error"
Increment (0.010000) does not make sense for range 0.001504..0.004851

[while trying to read-in 1SWASP+J211620.39%2B385538.6.fits]
"New Star From Observation Source Read Error"
Increment (0.010000) does not make sense for range 0.001859..0.007219

I assume that this is a relatively simple fix - possibly as easy as changing the default to a smaller number like 0.002 or 0.005 instead of 0.01. Another, somewhat smarter way to do it would be to allow 101 or 51 values in the spinner between the minimum and maximum magnitude errors.

I've attached the two FITS files for testing.

Discussion

  • David Benn
    David Benn
    2011-01-07

    Doug has checked this fix. We now need to add the fixed jar to the plugins library page.

     
  • David Benn
    David Benn
    2011-03-01

    I think this one can be closed, right?

     
  • David Benn
    David Benn
    2011-03-01

    • status: open --> open-fixed
     
  • Sara Beck
    Sara Beck
    2011-03-01

    Yep. This has been fixed and tested.

     
  • Sara Beck
    Sara Beck
    2011-03-01

    • status: open-fixed --> closed-fixed