https://github.com/access-community-hub/land-ancillary-creation

A repository containing scripts to create ancillary files for land surface models for ACCESS

https://github.com/access-community-hub/land-ancillary-creation

Science Score: 26.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • 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 (15.0%) to scientific vocabulary
Last synced: 10 months ago · JSON representation

Repository

A repository containing scripts to create ancillary files for land surface models for ACCESS

Basic Info
  • Host: GitHub
  • Owner: ACCESS-Community-Hub
  • Default Branch: main
  • Homepage:
  • Size: 272 KB
Statistics
  • Stars: 0
  • Watchers: 3
  • Forks: 0
  • Open Issues: 14
  • Releases: 0
Created over 1 year ago · Last pushed about 1 year ago
Metadata Files
Readme

README.md

About

This repository is intended to store, where appropriate, the many scripts and tools used by the land community within Australia as part of their research for ancillary data creation. This includes processes such as re-gridding, aggregation and disaggregation, statistical analyses and reductions, resampling, reformatting of datasets for ingestion by either CABLE or JULES. The goal is to use these community-shared resources to converge towards a shared infrastructure to create ancillary data.

This repository was first created for the working bee day at the 2024 Land Surface Model Working Group workshop.

Why

Many groups within the land community are using similar workflows and have similar requirements. By collecting and cataloguing the tools created by the community in one place, we achieve the following objectives:

  • Reduce duplicated work by reusing existing functionality
  • Ensure comparability between scientific runs made by different groups by using unified methods of interpolation, aggregation etc.
  • Results are reproducible, as we have a history of any changes made to the tools

What to do

Place your script or tool in the relevant directory within the repository and include a README. The README should be named according to the name of your script e.g. if your script is called interpolate_met_data.py, then your README should be named interpolate_met_data_README.txt.

Contents of the README

The README should have three headings: Purpose, Usage, Method. Please be verbose in the descriptions. For example:

Purpose

BAD: Interpolates met data

GOOD: Interpolates the CRU-JRA met data to the desired resolution and writes the output to NetCDF in a format readable by CABLE.

Usage

BAD: interpolatemetdata.py -r latresolution,lonresolution -o output.nc -b latmin,latmax,lonmin,lonmax

GOOD: Call from the command line via interpolate_met_data.py -r lat_resolution,lon_resolution -o output.nc -b lat_min,lat_max,lon_min,lon_max, where: * "-r latresolution,lonresolution" are the grid spacings (required). * "-o output.nc" specifies the name of the output file to write to (required). * "-b latmin,latmax,lonmin,lonmax" specify the domain to interpolate (optional). If no bounds are specified, then the original domain is used.

Method

BAD: uses linear interpolation

GOOD: Reads the dataset using xarray and uses scipy's LinearNDInterpolator to perform the interpolation.

Repository Structure

The repository is currently structured to reflect the categories set on the working day i.e. ancillaries and meteorological forcing. The structure for this repository (or it's successor) will be open to discussion.

Repository Structure (and potential further categorisations)

Owner

  • Name: ACCESS Community Hub
  • Login: ACCESS-Community-Hub
  • Kind: organization
  • Email: access.nri@anu.edu.au
  • Location: Australia

Australian Earth System Simulator Community

GitHub Events

Total
  • Delete event: 2
  • Issue comment event: 5
  • Push event: 45
  • Pull request review event: 2
  • Pull request event: 8
  • Create event: 6
Last Year
  • Delete event: 2
  • Issue comment event: 5
  • Push event: 45
  • Pull request review event: 2
  • Pull request event: 8
  • Create event: 6

Issues and Pull Requests

Last synced: 10 months ago

All Time
  • Total issues: 0
  • Total pull requests: 4
  • Average time to close issues: N/A
  • Average time to close pull requests: 21 days
  • Total issue authors: 0
  • Total pull request authors: 1
  • Average comments per issue: 0
  • Average comments per pull request: 0.0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 0
  • Pull requests: 4
  • Average time to close issues: N/A
  • Average time to close pull requests: 21 days
  • Issue authors: 0
  • Pull request authors: 1
  • Average comments per issue: 0
  • Average comments per pull request: 0.0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
Pull Request Authors
  • Whyborn (4)
  • ccarouge (1)
Top Labels
Issue Labels
Pull Request Labels