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
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (12.8%) to scientific vocabulary
Keywords
Repository
Python wrapper to parallelize GAMIT executions
Basic Info
- Host: GitHub
- Owner: demiangomez
- License: bsd-3-clause
- Language: Python
- Default Branch: master
- Size: 8.77 MB
Statistics
- Stars: 50
- Watchers: 5
- Forks: 25
- Open Issues: 39
- Releases: 37
Topics
Metadata Files
README.md
Parallel.GAMIT
A Python wrapper to manage GNSS data and metadata and parallelize GAMIT executions
Author: Demián D. Gómez
Parallel.GAMIT (PGAMIT) is a Python software solution for parallel GNSS processing of large regional or global networks. It incorporates a metadata and RINEX data management tool that guarantees a consistent archive. It relies on Postgres SQL (https://www.postgresql.org/) to store station metadata and the GPSPACE Precise-Point-Positioning (PPP) software (see installation instructions) to obtain reliable daily a-priori coordinates for GAMIT.
The software can be installed as a Python package (see INSTALL.md) allowing to import modules to perform time series analysis and extraction of trajectory parameters from the database.
PGAMIT also includes a backend (see branch web-ui-backend) and web frontend (see branch web-ui-frontend) that can be easily deployed to edit station related metadata (such as observation files and pictures) and processing metadata. The backend was developed in django and the frontend was developed using node.js.
PGAMIT uses dispy (https://github.com/pgiri/dispy) to create Python pickles that are sent to local or remote nodes for execution. PGAMIT has the ability to split a network of GNSS stations into subnetworks for processing in GAMIT (when the network is larger than 50 stations, depending on PGAMIT's configuration). The parallel execution is performed per day-subnetwork. In other words, a GAMIT pickle is built for each subnetwork-day being processed and sent to the available nodes. At the end of each PGAMIT run, the subnetworks are combined with GLOBK and inserted as records in the Postgres database for later use. Some routines (such as the SINEX parser) are modified versions of the code from @softwarespartan (https://github.com/softwarespartan).
Some of the tasks that PGAMIT can perform include:
- Scan a directory structure containing RINEX files and add them to the Postgres database.
- Manage station metadata in GAMIT's station info format with consistency check of the records.
- Add new RINEX data to the database by geolocation, i.e. the data is incorporated not by station name but by running PPP and finding the corresponding station in the DB. This avoids problems with duplicate station codes and misidentified RINEX files.
- Handle ocean loading coefficients to correct the PPP and GAMIT coordinates.
- Plot PPP time series using Bevis and Brown's (2014) extended trajectory model.
- Manage (i.e. add, merge, delete) GNSS stations.
- Parse zenith tropospheric delays and store them in the database.
- Stack the GAMIT solutions to produce regional or global reference frames following Bevis and Brown's (2014) and Gómez et al (2022).
- Station name duplicate-tolerance by using a three-letter network code. Although this is not supported by GAMIT, PGAMIT converts duplicate station codes (stored in different networks) to unique IDs that are used during processing, which are later converted back to the original names after the GLOBK combination of the subnetworks.
- Because all the information is stored in a relational database, PGAMIT can handle very large datasets easily (it has been tested with ~ 14M station-days but Postgres can easily handle more than 100 million records). Also, the relational database guarantees then consistency of the data and does not allow accidental duplicates in metadata.
Owner
- Name: Demian Gomez
- Login: demiangomez
- Kind: user
- Location: Columbus, OH
- Company: Division of Geodetic Science, School of Earth Sciences, The Ohio State University
- Website: https://earthsciences.osu.edu/people/gomez.124
- Twitter: ddgomez11
- Repositories: 3
- Profile: https://github.com/demiangomez
I'm a geophysicist and a geometrical geodesist doing active research on reference frame realizations, both regional and global.
Citation (CITATION.cff)
cff-version: 1.2.0 message: "If you use this software, please cite it as below." authors: - family-names: "Gómez" given-names: "Demián" orcid: "https://orcid.org/0000-0002-5276-581X" title: "Parallel.GAMIT" version: 1.2.2 date-released: 2017-12-18 url: "https://github.com/demiangomez/Parallel.GAMIT"
GitHub Events
Total
- Create event: 37
- Release event: 31
- Issues event: 156
- Watch event: 11
- Delete event: 11
- Issue comment event: 135
- Push event: 171
- Gollum event: 19
- Pull request review event: 26
- Pull request review comment event: 11
- Pull request event: 56
- Fork event: 3
Last Year
- Create event: 37
- Release event: 31
- Issues event: 156
- Watch event: 11
- Delete event: 11
- Issue comment event: 135
- Push event: 171
- Gollum event: 19
- Pull request review event: 26
- Pull request review comment event: 11
- Pull request event: 56
- Fork event: 3
Issues and Pull Requests
Last synced: 4 months ago
All Time
- Total issues: 56
- Total pull requests: 11
- Average time to close issues: 2 months
- Average time to close pull requests: 2 days
- Total issue authors: 5
- Total pull request authors: 4
- Average comments per issue: 0.86
- Average comments per pull request: 0.55
- Merged pull requests: 5
- Bot issues: 0
- Bot pull requests: 3
Past Year
- Issues: 54
- Pull requests: 11
- Average time to close issues: 2 months
- Average time to close pull requests: 2 days
- Issue authors: 5
- Pull request authors: 4
- Average comments per issue: 0.81
- Average comments per pull request: 0.55
- Merged pull requests: 5
- Bot issues: 0
- Bot pull requests: 3
Top Authors
Issue Authors
- demiangomez (88)
- marafigue (14)
- Salacas (8)
- espg (8)
- francosobrero (4)
- pomath (4)
- francolau (2)
- smalleyr (2)
Pull Request Authors
- espg (21)
- MarkusHackspacher (13)
- demiangomez (8)
- dependabot[bot] (6)
- Bembb (2)
- Salacas (2)
- pdsmith90 (2)
Top Labels
Issue Labels
Pull Request Labels
Packages
- Total packages: 1
-
Total downloads:
- pypi 1,201 last-month
- Total dependent packages: 0
- Total dependent repositories: 0
- Total versions: 42
- Total maintainers: 2
pypi.org: pgamit
A Python wrapper to parallelize GAMIT executions
- Homepage: https://github.com/demiangomez/Parallel.GAMIT
- Documentation: https://pgamit.readthedocs.io/
- License: BSD 3-Clause License Copyright (c) 2024, Demian Gomez Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
Latest release: 1.2.42
published 4 months ago