-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inaccurate get_source_ra_dec
results
#25
Comments
Example of issue:
|
For whatever reason, the ra/dec return value was being rounded to 3 decimal places in Java-land. I have updated this class. Please restart the REST server whenever is an opportune time to reload the change and let me know the result. |
Solved, closing issue |
@tkoumrian opening this again.
another source:
I checked and the errors are around what is expected for rounding point errors if using IEEE float32 for the computations. |
I recall the return value from Java is float32 not sure about the computation. I’ll have another look.
I checked and the errors are around what is expected for rounding point errors if using IEEE float32 for the computations.
Might that be correct?
—
Reply to this email directly, view it on GitHub<#25 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AM44SQIVDR3L643EJFRCNBDVCNHTZANCNFSM5RCUFNEQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Good news, the ra/dec calculation is in double, so I just need to propagate that up through the layers instead of float. |
@wfarah I've restarted the REST server and it should be returning Java double ra/dec values. See if that helps. |
Inconsistancy addressed in https://github.com/SETIatHCRO/restgw/issues/2 |
ata_control.get_source_ra_dec
(https://github.com/SETIatHCRO/ATA-Utils/blob/master/pythonLibs/ATATools/ata_control.py#L162-L189) is returning values that are apparently only accurate to 3 decimal parts.Assuming a rounding is happening, a maximum error of 0.0005 would result in RA and Dec. RA is expressed in hours, and so the effect would be ~27 arcseconds, whereas dec would be 1.8 arcseconds.
The digitizer board delay engine uses this utility function to phase center the array, thus these values have to be accurate to sub-arcsecond level.
The text was updated successfully, but these errors were encountered: