-
Notifications
You must be signed in to change notification settings - Fork 22
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
gmag bug in quickcat? #251
Comments
I don't know if that's a bug. It looks like it is one. |
Apologies, I thought you wrote |
Don't worry! |
I had a quick look and I'm not sure it's a bug (but I should check this in more detail): as far as true_gmag and qso_gmag_threshold are in the same units (nanomaggies), the flux ratio should be expressed as it is on line 218 (i.e., it should only depend on the difference true_gmag - qso_gmag_threshold). |
In fact you're right, this is a bug, true_gmag is a flux in nanomaggies and should be converted into a magnitude before being used in line 218. |
OK, great. I've fixed this in my branch and will merge after Stephen's PR.
…On Aug 1, 2017 7:30 PM, "cballand" ***@***.***> wrote:
In fact you're right, this is a bug, true_gmag is a flux in nanomaggies
and should be converted into a magnitude before being used in line 218.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#251 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABXZDHaqZj9YJqP_8krMhlFXAAF273e5ks5sT7T9gaJpZM4Opu4P>
.
|
Ok, thanks @moustakas |
Fixed in #252. |
@forero Is this code block in
quickcat
a bug?DECAM_FLUX
returns fluxes in nanomaggies but line 218 treats the g-band flux as a magnitude.[If this is indeed a bug I can fix it on the branch I'm working on now, which is updating the
targets
andtruth
tables to the latest imaging data model.]The text was updated successfully, but these errors were encountered: