Update CCPP variable pdf files for SCM v4.0 and UFS v1.0 release.#274
Conversation
climbfuji
left a comment
There was a problem hiding this comment.
This PR is totally fine with me, but need corresponding PRs to update the submodule pointers in fv3atm and ufs-weather-model.
|
Thank you for updating these PDFs. Can you also remove the unnecessary files in these directory and leave just the PDFs? |
|
url = https://github.com/NOAA-EMC/fv3atm
branch = release/public-v1
tag = ufs-v1.0.0
repo_url = https://github.com/ufs-community/ufs-weather-model/
…On Thu, Mar 26, 2020 at 1:32 PM ligiabernardet ***@***.***> wrote:
Thank you for updating these PDFs. Can you also remove the unnecessary
files in these directory and leave just the PDFs?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#274 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA3WNU3VCLMT3QNHDAOFDDTRJOUVNANCNFSM4LUOW65Q>
.
|
|
If I was really picky I would say we should move the PDFs one level up to the doc directory, but this requires changing the CCPP prebuild config in fv3atm (not a big deal, though) and various pieces of documentation that refer to those PDFS. Maybe not for the UFS v1.x.y release(s), but when we make the corresponding change for the master branch we should consider this. Also, can you confirm that without the makefile etc in the DevelopersGuide directory, one can create the PDF by running |
|
Yes, the pdf files can be created from the CCPP_VARIABLE_*.tex files
without the makefile, etc. There are currently no instructions in the Tech
Doc for making these files. I added a README.md files with instructions.
I think we can leave the files in this directory, since in the future,
these may be generated by the ccpp_prebuild.py file in some other format
(like rst) and converted to html and pdf in another manner.
…On Thu, Mar 26, 2020 at 3:16 PM Dom Heinzeller ***@***.***> wrote:
If I was really picky I would say we should move the PDFs one level up to
the doc directory, but this requires changing the CCPP prebuild config in
fv3atm (not a big deal, though) and various pieces of documentation that
refer to those PDFS. Maybe not for the UFS v1.x.y release(s), but when we
make the corresponding change for the master branch we should consider this.
Also, can you confirm that without the makefile etc in the DevelopersGuide
directory, one can create the PDF by running pdflatex? Are the
instructions in the CCPP technical documentation consistent with this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#274 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA3WNU4PODYUQ6MBLYINTV3RJPAY7ANCNFSM4LUOW65Q>
.
|
No description provided.