-
Notifications
You must be signed in to change notification settings - Fork 24
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
Finding out why islands are flagged #139
Comments
That's a good idea -- I'll look into adding the flag value to that list. Currently, you can see the flag value with the |
Hmm, there must be a bug in |
Thanks, if you need any additional information, please let me know. |
Strangely, I cannot reproduce the issue with At any rate, I added the flag values to the output. Let me know if it doesn't work for you (you need rebuild with the current master to pick up the changes). |
They never show for me, but I might be using an old version of PYBDSF? (It's currently installed on machines that use python2 as default) I tried to install the newest version from the master branch, but I am getting some errors related to a missing boost library... PYBDSF should work for python3 right? Thanks. |
Yes, both Python 2 and 3 are supported. Boost issues are a common problem with PyBDSF installations, unfortunately. |
If I understand it correctly from the documentation, when fitting Gaussians to islands of emission, a flag value is being saved inside the fitting code. After fitting, I usually also get the message
WARNING: All Gaussians were flagged for the following islands:
It would be a nice addition if on that list of flagged islands, the flag value or perhaps also the reason why they are being flagged is printed. As I understand it, there is no way to find the flag value after the fitting so the only way to find out why a source is being flagged is by changing the flagging parameters.
Thanks,
Erik
The text was updated successfully, but these errors were encountered: