hyp3-docs

Documentation for HyP3 products and services

https://github.com/asfhyp3/hyp3-docs

Science Score: 75.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
    Found 3 DOI reference(s) in README
  • Academic publication links
    Links to: zenodo.org
  • Academic email domains
  • Institutional organization owner
    Organization asfhyp3 has institutional domain (hyp3-docs.asf.alaska.edu)
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (12.1%) to scientific vocabulary
Last synced: 6 months ago · JSON representation ·

Repository

Documentation for HyP3 products and services

Basic Info
Statistics
  • Stars: 19
  • Watchers: 13
  • Forks: 12
  • Open Issues: 13
  • Releases: 143
Created over 5 years ago · Last pushed 6 months ago
Metadata Files
Readme Changelog Contributing License Citation Codeowners

README.md

HyP3 documentation

DOI

HyP3 documentation is built using MkDocs and the ASF Theme.

How to

Setting up a development environment

In order to automatically document some of our APIs, we use a conda environment with our APIs installed. You can get Miniconda (recommended) here:

https://docs.conda.io/en/latest/miniconda.html

Once conda is installed, from the repository root, you can create and activate a conda environment with all the necessary dependencies

conda env create -f environment.yml conda activate hyp3-docs

Later, you can update the environment's dependencies with

conda env update -f environment.yml

Build and view the documentation site

With the hyp3-docs conda environment activated, run

mkdocs serve

to generate the documentation. This will allow you to view it at http://127.0.0.1:8000/. MkDocs will automatically watch for new/changed files in this directory and rebuild the website so you can see your changes live (just refresh the webpage!).

Note: mkdocs serve captures your terminal; use crtl+c to exit. It is recommended you use a second/dedicated terminal so you can keep this command running.

Deploy

This documentation site is deployed as a GitHub Organization website with a CNAME so that it's viewable at https://hyp3-docs.asf.alaska.edu/. The website is served out of the special https://github.com/ASFHyP3/ASFHyP3.github.io repository. Deployment is handled automatically with the .github/workflows/deploy_to_github_io.yml GitHub Action for any merge to main.

There is also a test site deployed to https://hyp3-docs.asf.alaska.edu/hyp3-docs, which tracks the develop branch of this repo and is served out of the gh-pages branch of this repo.

Enable or disable the announcement banner

We can display a site-wide banner for important announcements. The content of this banner is specified in overrides/main.html, which should contain the following placeholder text when the banner is not in use:

```html {% extends "partials/main.html" %}

{# Uncomment this block to enable the announcement banner: {% block announce %}

⚠️ TODO: Your announcement here.
Read the full announcement.
{% endblock %}

}

```

In order to enable the banner, uncomment the announce block and fill in the TODOs. Below is an example of an enabled announcement banner (taken from here):

```html {% extends "partials/main.html" %}

{% block announce %}

⚠️ Monthly processing quotas were replaced by a credit system on April 1st.
Read the full announcement.
{% endblock %} ```

When the announcement is no longer needed, restore the file to the placeholder text in order to disable the banner.

If you are building and viewing the site locally, you will need to exit with ctrl+c and then re-run mkdocs serve in order to re-render any changes you make to this file.

Markdown formatting

The way MkDocs and GitHub parse the markdown documents are slightly different. Some compatibility tips:

  • Raw links should be wrapped in angle brackets: <https://example.com>
  • MkDocs is pickier about whitespace between types (e.g., headers, paragraphs, lists) and seems to expect indents to be 4 spaces. So to get a representation like:


    • A list item

      ##### A sub list heading

      • A sub-list item

    in MkDocs, you'll want to write it like:

    Good

    ``` - A list item

    ##### A sub list heading
    - A sub-list item
    

    ```

    Bad

    - A list item ##### A sub list heading - A sub-list item

    - A list item ##### A sub list heading - A sub-list item

    ``` - A list item

    ##### A sub list heading - A sub-list item ```

Owner

  • Name: HyP3
  • Login: ASFHyP3
  • Kind: organization
  • Location: Fairbanks, AK

Alaska Satellite Facility's Hybrid Pluggable Processing Pipeline

Citation (CITATION.cff)

cff-version: 1.2.0
message: If you use this software, please cite it as below.
authors:
- family-names: Hogenson
  given-names: Kirk
- family-names: Kristenson
  given-names: Heidi
  orcid: https://orcid.org/0000-0002-2130-4527
- family-names: Kennedy
  given-names: Joseph
  orcid: https://orcid.org/0000-0002-9348-693X
- family-names: Johnston
  given-names: Andrew
- family-names: Rine
  given-names: James
- family-names: Logan
  given-names: Thomas
  orcid: https://orcid.org/0000-0002-6982-0344
- family-names: Zhu
  given-names: Jiang
  orcid: https://orcid.org/0000-0001-6833-5518
- family-names: Williams
  given-names: Forrest
  orcid: https://orcid.org/0000-0001-8721-6020
- family-names: Herrmann
  given-names: Jake
- family-names: Smale
  given-names: Jacquelyn
  orcid: https://orcid.org/0000-0002-2749-5010
- family-names: Meyer
  given-names: Franz
  orcid: https://orcid.org/0000-0002-2491-526X
date-released: 2020-10-20
repository-code: https://github.com/ASFHyP3/hyp3-docs
title: "Hybrid Pluggable Processing Pipeline (HyP3): A cloud-native infrastructure for generic processing of SAR data"
doi: 10.5281/zenodo.4646138
license: BSD-3-Clause

GitHub Events

Total
  • Create event: 125
  • Issues event: 6
  • Release event: 20
  • Watch event: 5
  • Delete event: 99
  • Issue comment event: 70
  • Push event: 571
  • Pull request review comment event: 124
  • Pull request event: 248
  • Pull request review event: 202
  • Fork event: 4
Last Year
  • Create event: 125
  • Issues event: 6
  • Release event: 20
  • Watch event: 5
  • Delete event: 99
  • Issue comment event: 70
  • Push event: 571
  • Pull request review comment event: 124
  • Pull request event: 248
  • Pull request review event: 202
  • Fork event: 4

Issues and Pull Requests

Last synced: 6 months ago

All Time
  • Total issues: 4
  • Total pull requests: 125
  • Average time to close issues: 10 months
  • Average time to close pull requests: 4 days
  • Total issue authors: 3
  • Total pull request authors: 9
  • Average comments per issue: 1.25
  • Average comments per pull request: 0.42
  • Merged pull requests: 89
  • Bot issues: 0
  • Bot pull requests: 29
Past Year
  • Issues: 3
  • Pull requests: 125
  • Average time to close issues: 3 months
  • Average time to close pull requests: 4 days
  • Issue authors: 2
  • Pull request authors: 9
  • Average comments per issue: 1.33
  • Average comments per pull request: 0.42
  • Merged pull requests: 89
  • Bot issues: 0
  • Bot pull requests: 29
Top Authors
Issue Authors
  • jtherrmann (2)
  • feigl (2)
  • LiChiehLin (1)
  • jhkennedy (1)
  • asjohnston-asf (1)
  • KuangYF11 (1)
Pull Request Authors
  • dependabot[bot] (45)
  • hjkristenson (40)
  • tools-bot (26)
  • jtherrmann (24)
  • forrestfwilliams (16)
  • asjohnston-asf (15)
  • jacquelynsmale (12)
  • jhkennedy (6)
  • cirrusasf (4)
  • williamh890 (3)
Top Labels
Issue Labels
bug (5) Jira Bug (2)
Pull Request Labels
bumpless (82) patch (58) minor (36) tools-bot (15) documentation (11) major (4)

Dependencies

.github/workflows/changelog.yml actions
  • Zomzog/changelog-checker v1.0.0 composite
  • actions/checkout v1 composite
.github/workflows/check-links.yml actions
  • actions/checkout v3 composite
  • lycheeverse/lychee-action v1.5.4 composite
.github/workflows/deploy_to_github_io.yml actions
  • actions/checkout v2 composite
  • conda-incubator/setup-miniconda v2 composite
.github/workflows/labeled-pr.yml actions
  • mheap/github-action-required-labels v1 composite
.github/workflows/release.yml actions
  • actions/checkout v2 composite
  • docker://antonyurchenko/git-release v3.5.0 composite
  • repo-sync/pull-request v2 composite
.github/workflows/spellcheck.yml actions
  • actions/checkout v3 composite
  • actions/upload-artifact v3 composite
  • tbroadley/spellchecker-cli-action v1 composite
.github/workflows/tag-release.yml actions
  • actions/checkout v2 composite
  • actions/setup-python v1 composite
  • actions/upload-artifact v2 composite
  • helaili/github-graphql-action 2.0.1 composite
.github/workflows/test-build.yml actions
  • actions/checkout v2 composite
  • conda-incubator/setup-miniconda v2 composite
.github/workflows/update_asf_tools_version.yml actions
  • actions/checkout v2 composite
  • repo-sync/pull-request v2 composite
.github/workflows/update_sdk_version.yml actions
  • actions/checkout v2 composite
  • repo-sync/pull-request v2 composite
environment.yml pypi
  • mkdocs-asf-theme >=0.2.3
  • mkdocs-macros-plugin *
  • mkdocs-redirects *
  • mkdocs-section-index *
  • mkdocstrings *
  • mkdocstrings-python *
  • pymdown-extensions ==9.3
.github/workflows/create-jira-issue.yml actions
.github/workflows/release-template-comment.yml actions
.github/workflows/static-analysis.yml actions