Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Install and test meorg_client to upload and analyze PLUMBER2 and Urban-PLUMBER simulations

Open
#4,271 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
fortran
Domain
data

Research direction

Read the linked meorg_client installation and CLI documentation, then consult the notes at /glade/work/oleson/meorg_client/README_KEITH. The issue reports a successful upload and analysis but leaves the next dataset and scope undecided. Done would mean uploading and analyzing a selected recent Urban-PLUMBER or PLUMBER2 simulation set; the issue does not specify which one.

Written by the indexing model from the issue text.

Description

diagnostic enhancement next

I've been working on installing and testing the meorg_client (the ModelEvaluation.org client). Documentation on installing the client is here:
https://meorg-client.readthedocs.io/en/latest/contributing/
Documentation on uploading model files and initiating analyses from the command line is here:
https://meorg-client.readthedocs.io/en/latest/cli/

The documentation turns out to be not quite correct, so I met with Abhass Goyal at the Australian National University. We were able to upload a model file and run an analysis successfully.
My notes on this are at /glade/work/oleson/meorg_client/README_KEITH. Abhass will update the documentation.
Next steps may be to upload a set or sets of recent Urban-PLUMBER simulations I've done in support of Sean's water tracer work. Or upload a recent set of PLUMBER2 simulations I've done as part of the run_tower modifications PR.

Dominant language
Fortran
Stars
352
Forks
365
Avg merge
2d 14h
Merged PRs (30d)
13

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ESCOMP/CTSM

All issues in ESCOMP/CTSM

Similar issues

More Data Engineering issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.