2024-02-02 - February 2, 2024

[dprincz]

Updates

• @AlaBahrami has completed the runs with r1860_ME for the vector-based approach
• @AlaBahrami is waiting for the grid-based version of the Fraser with r1860_ME
• Al connected with Zelalem who remarked any changes he's made are incorporated in r1860_ME code
• @dprincz is about halfway connecting the r1860_ME changes to the GitHub code (the working repo is here: https://github.com/dprincz/MESH-Dev/tree/r1860-ME)
• Al talked to Mohamed Ahmed using an older version of the code (r16xx or r17xx series)

Discussion

• @mee067 thinks there are still changes related to MOUNTAINMESH and FROZENSOILINFILFLAG in Zelalem's code that is not in r1860_ME (i.e., "r1860_ME_ZT")
• It's more likely the setups are using MOUNTAINMESH but the local changes are isolated to FROZENSOILINFILFLAG
• GWF runs are not using FROZENSOILINFILFLAG, so these changes can be omitted from the "GWF" version of the code
• Diagnostic thermal variables are commented because they slow the model run, but pending I/O and book-keeping issues might resolve this issue

Suggestions

• Option to have the model be able to read successive series of driving data datasets
• Ability for the model to query available files on the system (this depends on our baseline supported compiler version, which might not support standard modern Fortran capabilities that enable this capability)

Actions

• @AlaBahrami will confirm the grid-based version has been run using r1860_ME
• Al will reach out to Zelalem again to discuss the local changes that might still exist (per @mee067's comment)
• @dprincz continue integrating the r1860_ME changes on GitHub
• Al will keep in touch with Mohamed Ahmed regarding variable-contributing area code
• @AlaBahrami will open an issue for a feature request regarding reading successive series of driving data datasets

Future Topics

• USask Wiki and migration of technical documentation (https://github.com/MESH-Model/MESH-Releases/wiki) and general user documentation (https://wiki.gccollab.ca/MESH)