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.

Sign up for GitHub

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

Jump to bottom

T3.3.2.1: Missing Matches Maths Framework #79

Open
Onoddil opened this issue May 21, 2024 · 3 comments
Open

T3.3.2.1: Missing Matches Maths Framework #79

Onoddil opened this issue May 21, 2024 · 3 comments
Assignees
@Onoddil @Tim-Naylor
Milestone
D3.3.2

Comments

@Onoddil
Copy link
Collaborator

Onoddil commented May 21, 2024

Following a similar structure to D3.3.1, the initial step of D3.3.2 is to develop the mathematical background required to answer the required questions surrounding the identification of potential matches that were missed in an initial cross-match run, and assign relative probabilities to astrophysical (or telescope/pipeine-related) origins of the reason for objects not matching, such as high proper motion, data artefact, or transient outbursts.
@Onoddil Onoddil self-assigned this May 21, 2024
@Onoddil Onoddil added this to the D3.3.2 milestone May 21, 2024
@Onoddil Onoddil mentioned this issue May 21, 2024
Open
@tms-epcc
Copy link
Contributor

23/MAY/24

  • Tom and Tim working on this

@tms-epcc
Copy link
Contributor

15/AUG/24

  • this is with Tim now

@tms-epcc
Copy link
Contributor

tms-epcc commented Oct 3, 2024

03/OCT/24

  • no progress but this can wait so not a concern until January'25

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Onoddil Onoddil

@Tim-Naylor Tim-Naylor

Labels
None yet
Projects
None yet
Milestone
D3.3.2
Development

No branches or pull requests
3 participants
@Onoddil @tms-epcc @Tim-Naylor