Further formatting fixes to the PC2 and boundary-layer scheme docs ported from the UMDPs. - #523
MichaelWhitall wants to merge 126 commits into
Conversation
…CloudScheme.tex to convert the latex source to .rst format.
… extension! Updated syntax to use this for the first few equations.
…hon script written by copilot.
…eferecing, and re-applied the corrections using an automatic script (most things stay the same, but my tweaks to reduce line-lengths have been reveretd).
…s possible to label and reference the individual equations in sphynx.
…'t converted to .rst correctly) with correctly-formatted display-mode equations.
…erical application', (b) Corrected a stray wrong indent, (c) Remove colon from appendix section titles (messes-up when used in the label).
…pply automated changes from scratch. Needed to apply corrections to section references in tables.
…and get the literature citations to work...
…tomating the corrections to figures and figure cross-referencing (then re-applied the manual fixes from 8 April 2026 using git apply).
|
Re the missing section of the PC2 doc (when comparing the UMDP on github versus the UMDP on trac), Yash helped me get to the bottom of this here: Section 3.3.1 was actually deleted by my trac ticket 4703, which replaced it with new sections further down the doc. The key thing is, the docs hosted on trac at i.e. the trunk of the |
|
Following some feedback offline from Yaswant Pradhan (@yaswant), I've added the latest commit which fixes the UM code-structure diagram in the PC2 cloud-scheme doc (just formatting corrections; changing the content to reflect LFRic rather than UM is tbd in another PR). In particular, the original latex version of this colour-coded the subroutine names according to whether they're used by the Smith, PC2 or bimodal cloud-schemes, but the text colours hadn't ported into ReST. Text colour has now been re-implemented. |
…th square brackets (regex failed to match these so they were still broken).
…es of cite commands with square brackets / optional arguments containing note text.
|
Happy with the state of this for now - but as noted - this is simple port + fix problems rather than a full edit of the docs to make them suitable and relevant for LFRic. This should be done as a future PR |
Paul Barrett (paul-barrett)
left a comment
There was a problem hiding this comment.
happy that this is a useful and sensible stage to pass this. As noted a future PR should be opened that re-writes the Docs for LFRic and checks new links and references, etc.
Awesome thanks for this Paul, Looking at the approvals, its still down as awaiting an approval from Steve; mo-sabel, do you have any comments on this PR / changes you'd like to request? Cheers! |
|
The quality/resolution of Fig 1 is poor in my browser compared to the UMDP030 pdf. Probably related, but the cartoon cloud in the "Convection Model" box in Fig 1 appears white, compared to the grey gradient colour in UMDP030 |
Hi thanks Steve, |
|
Thanks for explaining Mike.
I don't have a strong preference. Maybe the original is better as it is portrait rather than landscape. Note that the new one doesn't have the grey cloud in my browser even when zooming in, but I don't think that is important. Can consider recreating the figure in a future revision (looks like it was mostly done in PowerPoint!)
|
Sorry about the grey-cloud; I've updated the files to include this in my public_html directory in linux: I'll try deleting it and remaking it... |
That looks like it is working now. I personally think the new version looks better. In particular, the pdf diagrams are much better |
…ite (sci/tech review request).
…ow updated to handle this).
…ed extra spacing and removal of mathrm from the l).
…ut to be a mistake inherited as-is from the original latex source so fixing manually).
|
Your CLA signature was found on the base branch, but you appear to have modified the CONTRIBUTORS.md file in this PR. Please do not edit the CONTRIBUTORS.md file. If you have already signed the CLA, revert changes to the file and your signature will be picked up. |
|
Thanks to Steve and Adrian for spotting a few more issues; see the latest commit which fixes them:
The built docs linked here are updated with these changes: https://wwwspice/~michael.whitall/umdp_format_fixes/science_guide/cloud_schemes/UMDP30_PC2CloudScheme.html |
Thanks Mike. No more changes from me. I am happy that this is a faithful reproduction of the original document. |
mo-sabel
left a comment
There was a problem hiding this comment.
I am happy that this is now a faithful reproduction of the original document
|
Yaswant Pradhan (@yaswant), just a heads-up this PR is now ready for code review :) Cheers! |
PR Summary
Sci/Tech Reviewer: Paul Barrett (@paul-barrett)
Code Reviewer: Yaswant Pradhan (@yaswant)
#450 and #465 made an initial port of the UM Documentation Papers describing the PC2 cloud-scheme and the Boundary-Layer scheme into the lfric_apps science guide. This involved fixing many formatting errors when converting the source from latex to Sphinx / ReStructureText. Subsequent to those PRs being lodged, further formatting problems have been found. This PR attempts to fix these problems:
**) or bold (****); to get these equations to display I needed to close the enclosing**or*before the math, then open it again afterwards. Where math was inside a bold (****) region, I've used latex \boldsymbol to make it render bold as intended.\\"u(for a u with double-dots above) fooled my script as the"was interpreted as the end of the field string, so author names containing this character were spuriously truncated.\cite[<some text>][]{<key>}, which is meant to put the citation in square brackets and optionally insert some note text. The existing instances of these were broken and didn't render at all.Copy of the built docs: science_guide/index.html#science-guide-index
closes #405
closes #451
Code Quality Checklist
****Only documentation is edited; the doc source should speak for itself without needing explanatory comments, but feel free to suggest if you'd like any clarifying comments in the source?**check_cr_approved won't pass until code review is approved.Testing
*****Only modified documentation; rose-stem not applicable.To test the changes, I have built the lfric_apps docs from the branch source. The build now gives no errors or warnings.
trac.log
Security Considerations
**I'm not aware of any security issues with the docs. Does anyone know if there are license implications though? The latex UMDPs that I'm porting from are private, whereas the lfric_apps docs that I'm porting to are open-access?Performance Impact
NA
AI Assistance and Attribution
I got M365 copilot to help update the python scripts which I'm using to automate the format corrections applied to the doc ReST source after running pandoc (and the scripts were largely written by copilot in the first place).
Documentation
This is a documentation-only PR
PSyclone Approval
NA
Sci/Tech Review
(Please alert the code reviewer via a tag when you have approved the SR)
Code Review