pca_analysis_sifter

The principal components are used to get the range in transmittance for the SIFTER algoritm to calculate SIF from TROPOMI

https://github.com/carlijnjalink/pca_analysis_sifter

Science Score: 31.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
  • DOI references
  • Academic publication links
  • Academic email domains
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (12.6%) to scientific vocabulary
Last synced: 10 months ago · JSON representation ·

Repository

The principal components are used to get the range in transmittance for the SIFTER algoritm to calculate SIF from TROPOMI

Basic Info
  • Host: GitHub
  • Owner: CarlijnJalink
  • License: mit
  • Language: Python
  • Default Branch: main
  • Size: 47.9 KB
Statistics
  • Stars: 0
  • Watchers: 1
  • Forks: 0
  • Open Issues: 0
  • Releases: 0
Created about 1 year ago · Last pushed about 1 year ago
Metadata Files
Readme License Citation

README.md

check output PCA analysis SIFTER

The goal of this repository is to analyze the Principal Component's (PC's) from the PC Analysis (PCA) results from the first step of the SIFTER algorithm, where PC's are generated to simulate transmittance over the Sahara, for the TROPOMI satellite.

The script reads PCA results from an HDF5 file, extracts the principal components (EOFs), and plots them against wavelength. You can visualize different PCA modes using the plot_pca() function.

Usage

To start, navigate to the top level of the PCAanalysisSIFTER repository. Run the script from within there.

python version = 3.12. Ensure you have installed the required dependencies (h5py, matplotlib, pathlib), you can do so using the environment.yml. Run the script to inspect the PCA file structure and generate plots. Modify the plot_pca() function call to plot a certain PCA, and determine whether to save it or not.

Project Structure

The project structure distinguishes three kinds of folders: - read-only (RO): not edited by either code or researcher - human-writeable (HW): edited by the researcher only. - project-generated (PG): folders generated when running the code; these folders can be deleted or emptied and will be completely reconstituted as the project is run.

``` . ├── .gitignore ├── LICENSE ├── README.md ├── requirements.txt ├── data <- All project data, ignored by git ├── docs <- Documentation notebook for users (HW) │ ├── manuscript <- Manuscript source, e.g., LaTeX, Markdown, etc. (HW) │ └── reports <- Other project reports and notebooks (e.g. Jupyter, .Rmd) (HW) ├── results <- results from previously run scripts │ ├── figures <- Figures for the manuscript or reports (PG) │ └── output <- Other output for the manuscript or reports (PG) └── src <- Source code for this project (HW)

```

Add a citation file

Create a citation file for your repository using cffinit

License

This project is licensed under the terms of the MIT License.

Owner

  • Login: CarlijnJalink
  • Kind: user

Citation (CITATION.cff)

cff-version: 1.2.0
message: "If you use this software, please cite it as below."
title: "My Research Software"
authors:
  - family-names: Druskat
    given-names: Stephan
    orcid: https://orcid.org/1234-5678-9101-1121
version: 2.0.4
date-released: 2021-08-11
doi: 10.5281/zenodo.1234
license: Apache-2.0
repository-code: "https://github.com/citation-file-format/my-research-software"

GitHub Events

Total
  • Issues event: 1
  • Watch event: 1
  • Push event: 10
  • Create event: 2
Last Year
  • Issues event: 1
  • Watch event: 1
  • Push event: 10
  • Create event: 2

Dependencies

requirements.txt pypi