https://github.com/greenbankobservatory/gbt-pipeline

The Green Bank Telescope data analysis pipeline
https://github.com/greenbankobservatory/gbt-pipeline

Last synced: about 16 hours ago
JSON representation

The Green Bank Telescope data analysis pipeline

• Host: GitHub
• URL: https://github.com/greenbankobservatory/gbt-pipeline
• Owner: GreenBankObservatory
• License: other
• Created: 2010-01-05T19:30:02.000Z (almost 15 years ago)
• Default Branch: master
• Last Pushed: 2024-09-16T13:27:01.000Z (2 months ago)
• Last Synced: 2024-09-17T15:23:35.564Z (2 months ago)
• Language: C
• Homepage: https://safe.nrao.edu/wiki/bin/view/GB/Gbtpipeline/WebHome
• Size: 5 MB
• Stars: 9
• Watchers: 3
• Forks: 4
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.txt

Awesome Lists containing this project

README

        
# README

This document aims to describe the process of installing a new change to the gbtpipeline environment

## What is gbtpipeline

Green Bank Telescope (GBT) calibration and mapping pipeline

This will connect to the gbtgridder. Imaging dependencies include idlToSdfits, Obit, parseltongue and AIPS.

https://safe.nrao.edu/wiki/bin/view/GB/Gbtpipeline/WebHome

Production environments are stored in ``/home/gbt7/pipeline``. Environments can be created using ``createPipelineEnv.bash``

## Sequence Diagrams

What happens when someone presses enter on ``$ gbtpipeline``?

```mermaid

sequenceDiagram

    participant B as /opt/local/bin/gbtpipeline

    participant C as /opt/local/stow/nrao-gb/bin/gbtpipeline

    participant D as /home/gbtpipeline/gbt-pipeline/src

    participant E as /home/gbt7/pipeline/release/bin/activate

    Note left of B: $ gbtpipeline 

    B ->> C: simlink

    C ->> D: calls gbtpipeline script

    D ->> E: source venv

    Note left of E: simlink to 'release' to current venv

    D ->> D: gbtpipeline.py: main

```

## Update the production version

### Get your changes

```

ssh pipeline@galileo

cd /home/gbtpipeline/gbt-pipeline

# get the latest updates

git pull origin release_1.5

# if a new release then get the new branch

git checkout release_

git pull

```

### Create a new venv

```

ssh monctrl@galileo

cd /home/gbt7/pipeline

# you need the reuirements to make the venv

cp /home/gbtpipeline/gbt-pipeline/requirements.txt .

/home/gbtpipeline/gbt-pipeline/createPipelineEnv.bash gbtpipeline-v-env

```

### Replace the release venv

```

# if not still in the correct env

ssh monctrl@galileo

cd /home/gbt7/pipeline

rm release

ln -s gbtpipeline-v-env release

```

### All done!

You should be set then. Your new changes and venv will be called by the op/local/bin/gbtpipeline setup. See above for an diagram of that process.