Skip to content

Refactor the fre make readme and move quickstart#792

Open
singhd789 wants to merge 19 commits intoNOAA-GFDL:mainfrom
singhd789:update-fremake-readme
Open

Refactor the fre make readme and move quickstart#792
singhd789 wants to merge 19 commits intoNOAA-GFDL:mainfrom
singhd789:update-fremake-readme

Conversation

@singhd789
Copy link
Copy Markdown
Contributor

Describe your changes

  • updating readme to (1) overview, (2) quickstart, (3) subtools structure

Issue ticket number and link (if applicable)

Checklist before requesting a review

  • I ran my code
  • I tried to make my code readable
  • I tried to comment my code
  • I wrote a new test, if applicable
  • I wrote new instructions/documentation, if applicable
  • I ran pytest and inspected it's output
  • I ran pylint and attempted to implement some of it's feedback
  • No print statements; all user-facing info uses logging module

Note: If you are a code maintainer updating the tag or releasing a new fre-cli version, please use the release_procedure.md template. To quickly use this template, open a new pull request, choose your branch, and add ?template=release_procedure.md to the end of the url.

@singhd789 singhd789 changed the title Refactor the fre make readme and add quickstart Refactor the fre make readme and move quickstart Mar 20, 2026
@codecov
Copy link
Copy Markdown

codecov bot commented Mar 20, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.12%. Comparing base (836559e) to head (1cbb8d2).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #792   +/-   ##
=======================================
  Coverage   84.12%   84.12%           
=======================================
  Files          71       71           
  Lines        4944     4944           
=======================================
  Hits         4159     4159           
  Misses        785      785           
Flag Coverage Δ
unittests 84.12% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 836559e...1cbb8d2. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@singhd789
Copy link
Copy Markdown
Contributor Author

Note: I thought there was something I wanted to update or change here but I can't remember what it was....

@singhd789 singhd789 marked this pull request as ready for review March 31, 2026 16:44
Copy link
Copy Markdown
Member

@ilaflott ilaflott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not entirely clear on the quickstart v. guide contrast here.

Usually a guide is more detailed compared to a quickstart, which glosses over things to just get you started.

@singhd789
Copy link
Copy Markdown
Contributor Author

I'm not entirely clear on the quickstart v. guide contrast here.

Usually a guide is more detailed compared to a quickstart, which glosses over things to just get you started.

I think I could add more the the guide to make it more comprehensive. The quickstart is mainly supposed to be instructions you could almost just copy and paste to follow along. Good point, I'll try to add to the guide for more detail


Use fre make subtools to checkout code, create a Makefile, and build a container:
### Container Build:
In order for the container to build successfully, the parallel checkout feature is disabled.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm, maybe parallel checkout example should be given above for the bare-metal build?

Copy link
Copy Markdown
Contributor Author

@singhd789 singhd789 Apr 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the bare-metal build, the parallel checkout is the default behavior. Do you think users would want to see a non-parallel checkout example for the bare-metal build?
(I added a note that it is the default behavior)

```

Use `fre make all` to do the job of all 3 subtools in one step:
### Run all of fremake:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"blackbox" fre make? maybe this should be at the top

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

made it "all-in-one"? Is this better? 😅

fre make all -y fre/make/tests/null_example/null_model.yaml -p hpcme.2023 -t prod --execute
```

## Subtools
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wondering if this section is needed...

Copy link
Copy Markdown
Contributor Author

@singhd789 singhd789 Apr 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oook, maybe you're onto something here. I forgot (and just re-found) that a [tools].rst files exists in the docs as well. I suppose we want to get rid of duplication.

(https://github.com/NOAA-GFDL/fre-cli/tree/main/docs/tools)

@ilaflott ilaflott removed the beta1 label Apr 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants