Skip to content
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

Use logistic regression scorer to partition your patch of sky into physical objects #31

Closed
MatthewJA opened this issue Sep 24, 2019 · 7 comments

Comments

@MatthewJA
Copy link
Owner

Each object will have some number of TGSS and NVSS components.

@MatthewJA
Copy link
Owner Author

Look at some of these. Are you missing components? Are you adding extras? etc

@daccordeon
Copy link
Contributor

Comparison below at 5 degree fov around J101436.8-270532.
I reckon that, as expected, we're adding lots more components, especially in the central large multi-object. I will find an example where we might be missing something (like some aged triple with the two "jet-like" blobs further apart and elongated).

torch_lr_partition.pdf

tgss_window
nvss_window

@MatthewJA
Copy link
Owner Author

Oh that's a super good plot. Great work!

(You're more likely to pick up too many components than too few. I suggest finding an example of a partitioning that is OK, and one that is not.)

@daccordeon
Copy link
Contributor

Thanks! Will search for two blobs close together with nothing else nearby as an OK example.
See #32

@daccordeon
Copy link
Contributor

This looks like a candidate for two aligned ellipses:
J121923+054926

Sometimes a blob is large enough to count as multiple sources, this is a not very interesting form of multi-component:
TGSS J153418.0+101644, etc.
NVSS J153418+101544, J153414+101647, J153417+101708, J153417+101821

Also, looked up the most distant radio galaxy (looks very boring):
TGSS J153049.9+104933, NVSS J153050+104931

@daccordeon
Copy link
Contributor

Here's one such case of single match partition which seems alright.
TGSS J104025.2-162920, NVSS J104025-162920
Why it hasn't jumped to the nearby blobs, I don't know, but I would agree with the label.

@daccordeon
Copy link
Contributor

Move to close this and issue #32

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants