You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, there's no good way in place to verify that the correct plate scale is being used so it's hard to compare LMI vs. GDR data on the same graph. Could just use raw pixels, but then there's the potential for pixel size differences too so plate scale is really the better/more useful option.
This might just be a limitation that needs to be addressed for LOCUS; it needs investigating and some thought
The text was updated successfully, but these errors were encountered:
In short, there's no good way to do this. For LOCUS, the PHOT equivalent should optionally just return the answer in either (or both!) arcseconds and pixels since the camera will automatically have access to the current binning factor as well as the plate scale (since both get put into the FITS header). Will either open an issue over there or just add it to the draft list.
astrobokonon
changed the title
Figure out if it's possible to figure out the binning status when grabbing analysis data
Figure out if it's possible to know the binning factors when grabbing analysis data
Nov 5, 2018
I'm going to go ahead and close this as wontfix; it's a tremendous can of worms. Better to plan for the future than spend more cycles on this. And the LOCUS future can provide a better foundation for collection of metrics of how people are observing rather than current anecdotal/self reports.
Right now, there's no good way in place to verify that the correct plate scale is being used so it's hard to compare LMI vs. GDR data on the same graph. Could just use raw pixels, but then there's the potential for pixel size differences too so plate scale is really the better/more useful option.
This might just be a limitation that needs to be addressed for LOCUS; it needs investigating and some thought
The text was updated successfully, but these errors were encountered: