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

CAM not getting the correct use case with a long name comspet

Open
#1,685 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Domain
hpc

Research direction

Start by reproducing the 398 setup with the long compset name and compare its automatic use-case selection with the alpha10c configuration. Check how CAM derives CAM_NML_USE_CASE, and consider the issue done when this compset selects 1850_cam_mt without requiring ./xmlchange.

Written by the indexing model from the issue text.

Description

In 398, I am using a longname compset:

1850C_CAM70%MT_CLM60%BGC-CROP_CICE_MOM6%MARBL-BIO_MOSART_CISM2%GRIS-EVOLVE_WW3_SESP

It doesn't get the correct use case out of the box and I had to add:

./xmlchange CAM_NML_USE_CASE=1850_cam_mt

398 uses alpha10c

Dominant language
No language data
Stars
93
Forks
186
Avg merge
5d 3h
Merged PRs (30d)
18

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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/CAM

All issues in ESCOMP/CAM

Similar issues

More HPC issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.