As was announced in [IGSMAIL-8431], the current term for the IGS Analysis Centre Coordinators will conclude at the end of 2024. This marks the end of two terms (8 years) that Geoscience Australia and MIT have jointly served in this role, consistently providing a set of IGS combined products, in particular ultra-rapid, rapid, final and reprocessing orbits, clocks and ERPs.
The current call and transition plan to a new ACC involve the transfer of responsibility from GA and MIT to the new host(s), as well as the transition of the ACC software and analysis products. Please refer to the “Call for participation”, which provides a detailed introduction to the IGS ACC role, summary of resources and commitments required for the new ACC, minimum and preferred expectations from the new ACC, current status and plans for multi-GNSS ACC capabilities, an indicative timeline for the transition, and most importantly instructions for submitting a proposal to fill the role.
An Associate Member open meeting was held on 15 February to discuss Analysis Center Coordination and introduce the Call for Participation. A recording of the meeting is available on the IGS YouTube channel here: https://youtu.be/mhDKTJ7Ok3Q.
As per the transition plan, we request that institutes interested in the IGS ACC role submit their proposals to the IGS Central Bureau at cb [at] igs [dot] org. The deadline for submissions has been extended to 15 June 2024.
The current ACCs are available for consultation should potential interested organizations have questions not addressed in the call for participation document. Please contact acc [at] igs [dot] org for any inquiries in this matter.
Any further updates will be posted here and announced via IGSmail, LinkedIn, and Twitter.
[UPDATE]
Current cloud computing setup of the IGS ACC
Operation of the current IGS ACC is performed in the Amazon Web Service (AWS) cloud environment.
Main AWS services used include:
- EC2 instances: compute servers used for running the combinations
- S3 bucket: used for storage of the data/products
- Simple Email Service (SES): used for sending some of the ACC report emails
- Other services as required
The operational combinations are executed on AWS EC2 instances. Multiple EC2 instances serve various purposes. These instances are deployed across two AWS regions: one primarily designated for operational tasks and the other for experimentation, non-production, testing, and backup servers. This distribution of the operations across two geographically dispersed AWS regions provides redundancy and mitigates the risk of operational disruption due to events such as power outages, natural disasters, security breaches, or other unforeseen circumstances. This is an important aspect of the operations on multiple servers across different regions to keep the robustness of the IGS product combinations and ensuring the products remain available to the users.
The specifications of some of the main EC2 instances currently in use are listed below. All instances are in the Linux Operating System environment. Note the below specifications should only be considered as a guide on the general requirements for the IGS ACC, and a new ACC may decide on their setup as it best fits their workflow. Please refer to https://aws.amazon.com/ec2/instance-types/ for details of the different AWS EC2 instance types.
- Operational orbit, clock and ERP combinations:
- large EC2 instance: 2 vCPUs (up to 3.0 GHz Intel Turbo Scalable Processors), 8 GiB Memory
- Storage: 2 TB
- Download/Upload server:
- small EC2 instance: 1 vCPU, 0.5 GiB Memory
- Storage: 200 GiB
- Multi-GNSS demonstration server (currently producing ultra-rapid multi-GNSS combined orbits):
- medium EC2 instance: 2 vCPUs, 4 GiB Memory
- Storage: 300 GiB
- Non-product/test environment of the operational combination server:
- medium EC2 instance: 2 vCPUs, 4 GiB Memory
- Storage: 1.2 TB
- Other EC2 instances created on an “as-needed basis”, e.g. for the repro3 campaign or for development purposes. Such instances are often created but removed after the campaign is completed.
Regular back-ups (as Amazon Machine Images (AMIs) and Snapshots) are being created.
Last Updated on 18 Apr 2024 15:30 UTC