Science Score: 44.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
✓CITATION.cff file
Found CITATION.cff file -
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
○DOI references
-
○Academic publication links
-
○Committers with academic emails
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (13.0%) to scientific vocabulary
Repository
UVIT utility functions
Basic Info
- Host: GitHub
- Owner: prajwel
- License: apache-2.0
- Language: Python
- Default Branch: main
- Size: 18.6 KB
Statistics
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
- Releases: 1
Metadata Files
README.md
UVITility
A python package with UVIT-related utility functions.
You can install the UVITility Python package using the following command.
bash
pip install uvitility --upgrade
IMPORTANT: Even if you have UVITility already installed, make sure you use the latest version by running the above command. The current version of UVITility is shown on the badge below:
Check for centroid gaps in UVIT Level1 data
The UVIT-Payload Operations Centre (UVIT-POC) has come across (in June 2021) the presence of gaps in the X-centroids and shifts of 3 pixels (~10") in the Level1 (L1) data of UVIT. They are noticed for some orbits of a pointing. However, such gaps are not seen in the data of all OBSIDs. The presence of such gaps will lead to split images (separated by ~10") and shifted positions (by ~10") of sources in part of the field in the L2 images. This was found during the visual examination of L2 images carried out as part of the quality checks done by the POC. It appears that ~20% of OBSIDs have this issue, and of that 20% of the OBSIDs, ~10%% of the orbits are affected. At the moment, the UVIT-POC suggests caution that this problem could be present in any pointing during the whole history of observations, and individual PIs may like to look for it in their L1 data. The check_centroid_gaps function of UVITility can help to identify this defect.
After June 2021, in data sets where this issue is noticed, the POC has adopted the following approach. - identify the orbit with centroid gaps, - if gaps are found, remove that particular orbit (hereafter bad orbit), - create new merged L1 without the bad orbits and - run L2 on the new L1 and post the data back to ISSDC.
This approach will lead to the loss of L1 data and thus the creation of L2 images with less exposure time than the actual observations. Those OBIDs affected by this problem, among others, will have the following statement in the DISCLAIMER.txt file, which is part of the L2 bundle.
"The data acquired at some orbits of the observation has
gaps in X-centroids. In the L1 & L2 data downloadable
from ISSDC, those orbit data will be missing. In effect,
this has led to X% of loss in the acquired data."
The X% is calculated as follows, X% = (UVL1 - UVL1mod) * 100 / UVL1
where,
UV_L1 = original L1 file
UVL1mod = modified L1 file after removing corrupt data
The checks have NOT been carried out on L1 datasets processed at the UVIT POC and sent to ISSDC before July 1, 2021.
How to check the POC processing date of your L1 dataset: 1. Search for your dataset on the AstroBrowse website. 2. Download the data quality report XML file (
..._dqr.xml) by clicking on the 'Q' download flag adjacent to the 'L1' and 'L2' flags. 3. Open the XML file, and check the 'Creation_date' value.
If your data was processed and sent to ISSDC before July 1, 2021, we advise the users of UVIT data to check their L1 data for the defect using the check_centroid_gaps function of UVITility. It can be done as follows.
- Download the L1 dataset of your observation from ISSDC’s AstroBrowse website.
- Extract the compressed L1 dataset into a directory.
- Run the
check_centroid_gapsfunction on a Python command prompt or as a script. - Finally, check the plots produced by the
check_centroid_gapsfunction to determine whether your L1 dataset is affected by the gap problem.
A typical run of the check_centroid_gaps function to check for the problem will be as follows. The function will produce two plots for each orbit present in the L1 directory.
```python
import uvitility uvitility.checkcentroidgaps('path to the extracted L1 directory') ``` Note: The function attempts to detect the gaps automatically using an algorithm and prints the output. But the plots should always be checked to confirm whether the problem exists or not.
A sample set of plots from an affected orbit is shown below with explanations.
1. The first plot (..._stretched_data.png) shows a UVIT image stretched along the X and Y axes. The image stretched along the X-axis is shown on the left side of the plot across five panels (see the example figures below). Similarly, the right side of the plot shows the image stretched along Y-axis. Note that these images are without any corrections for the telescope drift. Notice a gap appearing on the left side on the 4th panel. The gap appears as an empty region of 8 subpixel width in the UVIT images. Such gaps may occur at any location in the image.

- The second plot produced (
..._stretched_data_histogram.png) is similar to the first plot. The difference is that it shows the image pixels collapsed along the Y and X-axes on the left and right sides, respectively. Notice the two peaks followed by the dip at the location of the gap.
Both plots together help to identify the presence of gaps in the UVIT orbits.
Requirements
UVITility works with Python 3.6 or later. UVITility depends on the following packages:
- astropy
- matplotlib
- numpy
Owner
- Name: Prajwel Joseph
- Login: prajwel
- Kind: user
- Website: https://prajwel.github.io/
- Twitter: Prajwel_Joseph
- Repositories: 5
- Profile: https://github.com/prajwel
Citation (CITATION.cff)
abstract: UVIT utility functions authors: - family-names: Prajwel Joseph cff-version: 1.2.0 date-released: '2024-01-02' doi: 10.5281/zenodo.10450291 license: - cc-by-4.0 repository-code: https://github.com/prajwel/uvitility/tree/v0.1.2 title: 'prajwel/uvitility: v0.1.2' type: software version: v0.1.2
GitHub Events
Total
- Issues event: 2
- Push event: 1
Last Year
- Issues event: 2
- Push event: 1
Committers
Last synced: almost 3 years ago
All Time
- Total Commits: 8
- Total Committers: 1
- Avg Commits per committer: 8.0
- Development Distribution Score (DDS): 0.0
Top Committers
| Name | Commits | |
|---|---|---|
| prajwel | p****j@g****m | 8 |
Issues and Pull Requests
Last synced: 6 months ago
All Time
- Total issues: 1
- Total pull requests: 0
- Average time to close issues: 14 minutes
- Average time to close pull requests: N/A
- Total issue authors: 1
- Total pull request authors: 0
- Average comments per issue: 0.0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 1
- Pull requests: 0
- Average time to close issues: 14 minutes
- Average time to close pull requests: N/A
- Issue authors: 1
- Pull request authors: 0
- Average comments per issue: 0.0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Top Authors
Issue Authors
- prajwel (1)
Pull Request Authors
Top Labels
Issue Labels
Pull Request Labels
Packages
- Total packages: 1
-
Total downloads:
- pypi 17 last-month
- Total dependent packages: 0
- Total dependent repositories: 0
- Total versions: 5
- Total maintainers: 1
pypi.org: uvitility
UVIT utility functions
- Homepage: https://github.com/prajwel/uvitility
- Documentation: https://uvitility.readthedocs.io/
- License: Apache Software License
-
Latest release: 0.1.3
published 12 months ago