feat: add lgar, sft, and smp modules

[aaraney]

Add nextgen realization models for LGAR, Soil Freeze Thaw, and Soil Moisture Profile modules.

ngen.config -- 0.2.6

Additions

• Add nextgen realization models for LGAR, Soil Freeze Thaw, and Soil Moisture Profile modules.

[hellkite500]

Add test cases, then we can merge.

[hellkite500]

Can you add Xia as a coathor to this commit bc913a3 and rebase?

Can add in the commit message trailer.
Co-authored-by: Name

[aaraney]

Can you add Xia as a coathor to this commit bc913a3 and rebase?

Can add in the commit message trailer. Co-authored-by: Name

Yep, done!

For those interested in doing this themselves, this was really helpful.

[aaraney]

Add test cases, then we can merge.

Yep, done!

[hellkite500]

Thinking about conventional commits, we should maybe adopt a version(major):, version(minor):, version(bug) convention, or some other set of version(context): prefixes to help parse history for version changes. We tend to use a lot of "bump" like commit messages as is, so having a defined set of tags to search for later might be nice.

[aaraney]

We tend to use a lot of "bump" like commit messages as is, so having a defined set of tags to search for later might be nice.

@hellkite500, I think what you want is right under your nose! I would advise using git tags for versions instead of relying on commits. For namespace packages, I am a fan of {namespace}.{package}/vM.m.P. To you point, in the future I hope we can remove the need to bump package _version.py files and solely rely on git for package versions. See #92 for a draft proposal of this.

[hellkite500]

Not sure you can ever get away from commits which change some text in the repo based on a version change. E.g change logs, release notes, ect. My previous comment was simply about a commit prefix that helps track down version info changes in the history using conventional commit strategies.

I agree git tags would be helpful, and a set of version commit prefixes may be prime candidates for which commits get tagged!

A git tag, after all, is still a commit...

[stcui007]

Depending on your intention, "TGS" might be a more appropriate variable for "ground_temperature".

…

On Wed, Mar 20, 2024 at 8:40 AM Nels ***@***.***> wrote: Not sure you can ever get away from commits which change some text in the repo based on a version change. E.g change logs, release notes, ect. My previous comment was simply about a commit prefix that helps track down version info changes in the history using conventional commit strategies. I agree git tags would be helpful, and a set of version commit prefixes may be prime candidates for which commits get tagged! — Reply to this email directly, view it on GitHub <#97 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACA4SRMB4I5CCFWUP5X5QJTYZGGUVAVCNFSM6AAAAABD2OU6RCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBZGU4TEMRUGE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>