CosmoStat / CosmoStat/shapepipe

[NEW FEATURE] Local position in the validation catalogue for MCCD

Open
#610 0 comments 1 reaction 1 assignee View on GitHub

@tobias-liaudat is already working on this.

Since Jan 26, 2023.

enhancement
Dominant language
Python
Stars
18
Forks
14
Avg merge
8h 40m
Merged PRs (30d)
10

Description

Hello,
I have noticed that in the MCCD catalogue the x and y positions are given on the global grid that MCCD is using for the multi-CCD approach. Due to this, the MCCD package is required to read the catalogue and transform back the positions to a local reference mining x and y on each CCDs. I think it could be nice to have the local positions directly in the catalogue to avoid the call to MCCD. That would simplify the validation a lot because the catalogue will follow the same format as PSFEx and we could have only one validation function instead of two. I think that could also simplify the comprehension of the catalogue by external users.

I see two ways to handle this:

  1. This can be done in the merge_starcat module but I found that a bit sub-optimal because we will have one function for MCCD catalogues and one for PSFEx (like it is right now).
  2. Do it in MCCD when it does the interpolation. Like that we could also simplify the merge_starcat module. What I would propose is just to add one column for the LOCAL_POS along side the GLOBAL_POS so the user can choose which one to. It will not break the pipeline as it is and give time to update the different modules that are impacted.

One solution is only in ShapePipe the other is in MCCD. I have a preference for the second one. Let me know what you think 🙂
(Maybe this issue should be moved to the MCCD repo, let me know)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.