Skip to content

update information in basics/cesm_workflow/case_* #12

Open

Description

@wwieder

The cesm workflow pages currently uses a cesm example

Definition of done:

  • Change subdir name from using cesm to ctsm
  • Change files with cesm in name to ctsm
  • Update toc with the above
  • Quick go through notebooks under basics
  • Quick go through notebooks under basics/ctsm_workflow
  • Quick go through basics/code/ctsm_code_explore.ipynb
  • Quick go through basics/*overview.ipynb
  • Careful go through notebooks under basics/exercises
  • Quick update of resources/github.html
  • create_newcase supported compsets and query_config command
  • Fix bad link to workspaces in basics/code/git_download_ctsm.html and exercise_overview
  • Remove TODO on images in create_newcase notebook
  • Update example build in case_build
  • Remove mention of SourceMods (make a seperate issue for this)
  • Have a central place where the tutorial tag can be set and used elsewhere (create a seperate issue for this)
  • Same for tutorial queue and project code (Update project account/tutorial queue in notebooks #26)
  • create_clone add a comment about making a shell_commands file that will be copied to other cases
  • Update resources/tutorial_one_time_setup
  • Update .profile and .tcshrc for CLM Tutorial
  • Some exercises have files that are turned into links, remove the link ability for these
  • Update images that need to be updated in basics: Update images thorughout notebooks #13
    • Workspace overview image could be redone (used more than once, although the thing highlighted changes)
    • Create_newcase image
    • Command arguments to create_newcase is fine
    • resolution for create_newcase should be redone for a CLM grid
    • compset for create_ncase should be redone for a CLM compset

Activity

  1. ekluzek commented on Oct 15, 2026

    @ekluzek
    Collaborator

    #43 took care of most of this. But, images still need to be dealt with. And there are some pages references like the git pages that still need to be handled.

  2. wwieder commented on Oct 15, 2026

    @wwieder
    CollaboratorAuthor

    @ekluzek is it simple enough to list the TODOS that need to be updated? Alternatively, if we're in good shape should we mark this as done?

  3. ekluzek commented on Oct 15, 2026

    @ekluzek
    Collaborator

    6. @ekluzek is it simple enough to list the TODOS that need to be updated? Alternatively, if we're in good shape should we mark this as done?

    I'll list the TODO's as checkboxes above in a definition of done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions