Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[NEW FEATURE]Dummy masked images

Open
  • Is something wrong?
#605 7 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@fabianhervaspeters is already working on this.

Since Jan 16, 2023.

Assessment

This issue has not been assessed yet.

Description

enhancement

The masking step, run_sp_MaMa, takes an external star catalog and then places masks over known bright stars that will saturate the CCDs, leave a halo, etc. Our simulated images dont contain saturated stars, and will not match to real bright stars anyway, since they are not images of the real sky, so we need to skip this step. We also need to create dummy mask files where every pixel is 0 for each exposure. We need to create dummy flags for both exposures AND tiles. Here are the steps to do this:
For exposures: I would add a step to the image splitting module

  1. Create an option in the config file that says whether or not you are running simulations. If you are running simulations, then do the following
  2. Create a single blank image that is the size of 1 ccd. All pixels should be integers and be set to 0. For every image in the individual exposures, create a link from this dummy image that takes on the corresponding name of the flag image: eg flag-2106087-9.fits would correspond to image-2106087-9.fits. The flags should be in the same directory as the split images.

For tiles, I would add the step to the uncompress module where the weight image is uncompressed.

  1. Create an option in the config file that says whether or not you are running simulations. If you are running simulations, then o the following
  2. Create a single blank image that is the size of 1 tile. All pixels should be itegers and be set to 0. Create a link from this dummy image for every tile with a name that replaces image.......fits to flag......fits

Now that you created the dummy flags, you need to set up the sextractor step of the pipeline. The config file currently looks for the flags created by the masking step that we skip with the name pipeline_flag.... . We need the pipeline to look for the regular flags that were created in the previous steps, so the config needs to be modified accordingly.

Dominant language
Python
Stars
18
Forks
14
Avg merge
1d 4h
Merged PRs (30d)
18

Getting set up

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.

More from CosmoStat/shapepipe

All issues in CosmoStat/shapepipe

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.