Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Pick error when changing radius
See original GitHub issueAs can be seen from the figure below, the pick gives error message after I change the radius for pick settings:
I guess this is because the radius changes into a float when I modify it, while ginga takes only integer radius.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
css - border-radius not working - Stack Overflow
to the element that I was applying the border radius to. Final working code: ... 7px setting is nullifying the border-radius. Change it...
Read more >Misleading error message when circle radius is NaN #4235
If a L.circle is created with proper coordinates but a radius that is NaN (e.g. L.circle([36.83711,-2.464459], NaN) )leaflet throws an error ...
Read more >RADIUS Issue Resolution Guide - Cisco Meraki
This article outlines the general troubleshooting methodology when an issue with RADIUS troubleshooting is encountered, and provides a flow ...
Read more >What does a “Shared secret is incorrect” error mean?
FreeRADIUS generally looks for the shared secret in the /etc/raddb/clients.conf file. If that is not where you are changing the shared secret, ...
Read more >Troubleshooting RADIUS Authentication/Authorization Issues
The following common configuration errors may result in RADIUS authentication failing: No certificate installed on the RADIUS Server or the ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@pllim, it actually does the FWHM fine. It was in an additional centroid calculation that the error with a float radius manifested itself. numpy doesn’t want to let you index arrays with floats (which makes sense).
I don’t think it is the radius. I can’t reproduce the error on my own image by setting radius to 9.0 as you did. Looks like FWHM calculation failed.
One thing you can do is save and post the Ginga log when you encounter this again.
ginga --loglevel=10 --log=ginga.log