-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated RDA addresses and dataset names #790
Conversation
Did not update ./CHANGELOG.rst ./_build/html/CHANGELOG.html ./_build/html/_sources/CHANGELOG.rst.txt These substitutions were made: sed \ -e "s#glade\/collections#glade\/campaign\/collections#" \ -e "s#edu\/ds\/#edu\/datasets\/ds#g" \ -e "s#ds345.0#d345000#g" \ -e "s#ds199.1#d199001#g" \ -e "s#ds090.0#d090000#g" \ -e "s#ds337.0#d337000#g" \ -e "s#ds285.0#d285000#g" \
Does not look like any html files in this pull request. Do you mean the .rst files? |
Apparently the files in _build/html/... are not under git control. I'm guessing those are exclude intentionally. |
Yes those are files from the local build of the documentation. |
How about for the .rst having one reference file for all the data sets so they only need to be changes in one place (when the rda links change, or change to dois). .. CAM6rean :: https://rda.ucar.edu/datasets/d345000/ .. CAM4rean :: https://rda.ucar.edu/datasets/whatever .. NCEPrda :: https://rda.ucar.edu/datasets/blahblah |
That would tidy some of the files nicely. But most of the files are stream files. |
Add this to conf.py them you can have a guide/references.rst (or whatever you want to call it) included in every file. This means you can use
|
In my conf.py I needed to activate the os package to make the references lines work. I also added |
@kdraeder do you want me to fix it or help you fix it? |
I'll just go ahead and fix this Kevin |
for RDA datasets: - cam6 rean d345 - cam 4 rean d199 - prepbufr d09 - wod d285
6e736a5
to
a67de0e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I switched the https://rda.ucar.edu/datasets links for targets in guide/references.rst.
I'm happy for this to be merged and released.
@braczka do you have any objections?
I'm still trying to figure out what you changed and how it compares with the work I did Friday, but didn't commit yet. My git skills are not the quickest.
|
these lines in the conf.py includes the guide/refrences.rst in every file
|
Here is what I changed: |
guide/references.rst Collected frequently used web addresses for convenient updating. conf.py Added lines to make references.rst available in all .rst files. models/POP/readme.rst models/cam-fv/readme.rst observations/obs_converters/WOD/WOD.rst Updated to use references.rst links.
WARNING: there are still many non-link references (d######) to RDA datasets. These will not be updated by changes to references.rst, if, for example, the RDA changes its dataset name convention again. Trying to continue the merge. I resolved the conflicts, ran `make html`, which noted undefined links to the entries in refs, because they used Helen's abbreviations. I fixed those ({clm,wrf}/tutorial/README.rst and prep_bufr.rst), and added them explicitly, since they weren't part of the 2 previous references.rst commits and didn't have any conflicts.
I pulled this commit already, but there were conflicts. I resolved them by editing all the conflicted files, committing them, and 'continue'ing the merge. It appeared to work. I did an explicit merge again and got the message that there was nothing to merge. I tried to push the changes, but was told again that there are upstream changes that need to be merged. But they are all the same as what I just merged (based on the time stamps. So I'm trying to pull them again, with a different command; `git pull -s ort -X ours upstream rda_refs`. I have little hope.
ok @kdraeder I guess you are doing the changes, I will redo the review. |
models/cam-fv/readme.rst
Outdated
|
||
The variety of research can be sampled on the DART | ||
`Publications <https://dart.ucar.edu/pages/Publications.html>`__ page. | ||
`Publications <https://dart.ucar.edu/pages/Publications.html>`_ page. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what's the goal of making this non-anonymous?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my limited reading I got the impression that anonymous is less robust, but now I see that it's an "embedded" URI and there are no other references to it (in this document), so anonymous is not any riskier than a named link or pointer. I'll revert it.
models/cam-fv/readme.rst
Outdated
is described in the `CESM readme <../CESM/readme.html>`_ | ||
This document focuses on the several `atmospheric models <http://www2.cesm.ucar.edu/models>`__ | ||
This document focuses on the several `atmospheric models <http://www2.cesm.ucar.edu/models>`_ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you updating all the links in this document?
If so, <../CESM/readme.html>`_ should be changed to not be html so it builds correctly with latex, etc. builds of the documentation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My goal was not to update all the links, but it seemed like I should fix link-related things that I noticed. My intent was the same as the Publications change (previous comment), but you've brought up a new issue - latex - so I'm wondering whether the html form is fine in an anonymous link (__) but not in a named link (_).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:doc:`CESM readme <../CESM/readme>`
will create a link that works in html (or pdf, or ps, or whatever is built)
The x.html links show up as broken links when you run a link checker (e.g. #799 ~355 broken links), so they are good to fix. That way it is easier to spot actually broken links (like an external site has moved)
if you want to get super tidy, you could get rid of the relative path (which will break if/when someone reorganizes the docs) you could add a target to the CESM/readme.rst file
.. _ CESMreadme
:ref:`CESMreade`
We have loads of relative links, so not super necessary at the moment.
The x.html links show up as broken links when you run a link checker, so they are good to fix
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd probably enjoy making it super tidy and maintainable, but I don't want to add that mission creep to this issue. I've opted for the :doc: form (in 3 places). Thanks for the tips!
models/cam-fv/readme.rst
Outdated
`DS345.0 <https://rda.ucar.edu/datasets/ds345.0/#!description>`__ . | ||
(See the |CAM6_Rean|_ ). | ||
`d345000 <CAM6rean_rda_>`_ . | ||
(See the `CAM6rean_wiki`_ for details). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You've changed the name of the link here. Main branch:
(See the 1 degree reanalysis wiki ).
This pull request:
(See the CAM6rean_wiki for details).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That was a reference formatting error. But the doc still refers to the wiki by different words. Is that a problem if the rst name of the link is consistent?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no not a problem just checking that you were ok with having the link test be CAM6rean_wiki vs 1 degree reanalysis wiki. Either seems ok to me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
edit: link text, not test
models/cam-fv/readme.rst
Outdated
Versions of these files, which also have the results of the reanalysis in them, | ||
are available from the RDA ds345.0 linked above. | ||
are available from the RDA d345000 linked above. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why not link here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When I first wrote it they were closer, and the extra typing didn't seem worthwhile. I've made it a link now.
Removed mistaken `include` rst commands. models/cam-fv/readme.rst There is a "Publications" link, so Removed the related ISSUE. models/POP/readme.rst
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work Kevin!
Thanks! and thanks for your suggestions. |
Description:
NCAR's Research Data Archive changed their dataset naming convention,
so all the references in DART became outdated.
The "local" (/glade) versions were also moved to a new location (/glade/campaign) when derecho replaced cheyenne.
Did not update
./CHANGELOG.rst
./_build/html/CHANGELOG.html
./_build/html/_sources/CHANGELOG.rst.txt
These substitutions were made:
sed \
-e "s#glade/collections#glade/campaign/collections#" \
-e "s#edu/ds/#edu/datasets/ds#g" \
-e "s#ds345.0#d345000#g" \
-e "s#ds199.1#d199001#g" \
-e "s#ds090.0#d090000#g" \
-e "s#ds337.0#d337000#g" \
-e "s#ds285.0#d285000#g" \
@hkershaw-brown I updated some .html files too, and would like confirmation that that was
the right thing to do.
@braczka Please check some of the CLM files, but I think that you don't need check all of them.
I did not add DOIs for these datasets, which would be more robust, but more work.
Fixes issue
#755
Types of changes
Documentation changes needed?
Tests
I checked the changes in
./models/POP/shell_scripts/cesm2_1/user_datm.streams.txt.CPLHISTForcing.Solar_template
I did not test any of the testable files.
Checklist for merging
Checklist for release
Testing Datasets