Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[NEW FEATURE]Dummy masked images

Abierto
  • ¿Algo no está bien?
#605 7 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@fabianhervaspeters ya está trabajando en esto.

Desde el 16/1/2023.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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.

Lenguaje dominante
Python
Estrellas
18
Forks
14
Merge medio
1 d 4 h
PR fusionados (30 d)
18

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CosmoStat/shapepipe

Todos los issues de CosmoStat/shapepipe

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.