You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The mosaic level pipeline page on readthedocs (https://roman-pipeline.readthedocs.io/en/latest/roman/pipeline/mosaic_pipeline.html)) only briefly mentions the source catalog step in the table, and does not mention the flux step at all. Right now there's no documentation I could find that lets users know the flux step is part of the mosaic pipeline.
Additionally, the docstring for the mosaic pipeline class ([https://github.com/spacetelescope/romancal/blob/main/romancal/pipeline/mosaic_pipeline.py]) does not list source catalog or flux in the list of steps the pipeline runs.
(Side note: this is my first time attempting to create an issue for romancal documentation, so it's highly likely I have made a misstep somewhere. Information on how to file issues like this correctly is very welcome, thank you in advance for your patience!)
The text was updated successfully, but these errors were encountered:
Issue RCAL-890 was created on JIRA by Samantha Hoffmann:
The mosaic level pipeline page on readthedocs (https://roman-pipeline.readthedocs.io/en/latest/roman/pipeline/mosaic_pipeline.html)) only briefly mentions the source catalog step in the table, and does not mention the flux step at all. Right now there's no documentation I could find that lets users know the flux step is part of the mosaic pipeline.
Additionally, the docstring for the mosaic pipeline class ([https://github.com/spacetelescope/romancal/blob/main/romancal/pipeline/mosaic_pipeline.py]) does not list source catalog or flux in the list of steps the pipeline runs.
(Side note: this is my first time attempting to create an issue for romancal documentation, so it's highly likely I have made a misstep somewhere. Information on how to file issues like this correctly is very welcome, thank you in advance for your patience!)
The text was updated successfully, but these errors were encountered: