Skip to content

Heading Changes for clarity#71

Open
AdrieneCope wants to merge 1 commit intoCIROH-UA:mainfrom
AdrieneCope:patch-1
Open

Heading Changes for clarity#71
AdrieneCope wants to merge 1 commit intoCIROH-UA:mainfrom
AdrieneCope:patch-1

Conversation

@AdrieneCope
Copy link
Contributor

@AdrieneCope AdrieneCope commented Feb 26, 2026

Updated text for clarity. Fixed a minor issue with the collapsible code section.

Additions

  • Line 10. Added a link to CIROH-UA's "About" page so new visitors can go there to learn more about what CIROH is. Here's the link:
  • Line 48, Line 50: Wrote out the name for AWS so people less familiar with Amazon Web Services know what that section is talking about.
  • Line 51. Split the information into separate sentences for clarity.

Removals

  • Line 38. Removed the smiley face next to "Logs." It didn't seem professional.

Changes

  • Line 32. added additional information about the "para_post-processed" folder.
  • Lines 73-132. Fixed some spacing issues with the drop down tab that was a problem with just the GitHub rendering of the page. It was hiding away the entire lower half of the page instead of just the code block but now it's fixed. However, the deployed page was just fine.
  • Line 139. Gave the title heading formatting.

Testing

Screenshots

Here is what the new link looks like:
Screenshot 2026-02-26 at 12 42 31 PM

Here's the dropdown page closed with the fixed code:
Fixed Dropdown closed

Here's the dropdown page opened with the fixed code:
Fixed dropdown open

Here's what it looked like before the fix with the tab opened. Note, it only looks this way in the GitHub rendering, it looked fine on the website.:
Broken Dropdown

Notes

-More updates coming.

Todos

Checklist

  • PR has an informative and human-readable title
  • Changes are limited to a single goal (no scope creep)
  • Code can be automatically merged (no conflicts)
  • Code follows project standards (link if applicable)
  • Passes all existing automated tests
  • Any change in functionality is tested
  • New functions are documented (with a description, list of inputs, and expected output)
  • Placeholder code is flagged / future todos are captured in comments
  • Visually tested in supported browsers and devices (see checklist below 👇)
  • Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
  • Reviewers requested with the Reviewers tool ➡️

Testing checklist

Target Environment support

  • Windows
  • Linux
  • Browser

Accessibility

  • Keyboard friendly
  • Screen reader friendly

Other

  • Is useable without CSS
  • Is useable without JS
  • Flexible from small to large screens
  • No linting errors or warnings
  • JavaScript tests are passing

Updated text for clarity. Fixed an issue with the dropdown tab. It was hiding the entire page instead of just the code block.
@AdrieneCope
Copy link
Contributor Author

@jameshalgren


Jupyter notebook instructions for processing NWM Zarr and NetCDF output formats [here](https://github.com/CIROH-UA/data_access_example/)

<details>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We realized the break is unnecessary <br/> so this commit removes it.
Curiously, the GitHub rendering of the break is a bit odd. If there isn't a space between the summary and the collapsed content, it will not render correctly. See below:

This is the rendering with proper spacing

There must be a space after this line for the collapsing to work correctly
#this is fake python for testing

print("Hello, World!")
This is a test showing the bad Github Rendering ```py #this is fake python for testing

print("Hello, World!")

</details>
When you expand the details, you can see the rest of the page is absorbed into the collapsed tab. 

This comment was marked as resolved.

Copy link
Collaborator

@Sheargrub Sheargrub left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look appropriate on average, but there were a few oddities that caught my eye.

# NWM Data Access

Within the CIROH projects, we encounter a wide range of data resources and data access inquiries. One of the most frequently asked questions is, "How can I obtain access to xyz-resource?". To help with answering that question, we have documented some of the most common data access methods and resources here, with links to additional sites to dive deeper.
Within the [CIROH projects](https://ciroh.ua.edu/about/), we encounter a wide range of data resources and data access inquiries. One of the most frequently asked questions is, "How can I obtain access to xyz-resource?". To help with answering that question, we have documented some of the most common data access methods and resources here, with links to additional sites to dive deeper.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you sure this link is necessary? Given the nature of CIROH Hub, it seems reasonable to treat the consortium itself as common knowledge for users who're this deep into the site.

- The catalog of AWS-hosted operational NWM data can be browsed [here](https://noaa-nwm-pds.s3.amazonaws.com/index.html).

The second (and more useful) AWS repository contains several versions of the retrospective dataset each described on the main page under the open data registry [here](https://registry.opendata.aws/nwm-archive/).
The second AWS repository contains several versions of the retrospective dataset each described on the main page under the open data registry [here](https://registry.opendata.aws/nwm-archive/).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Possible loss of information here. Is there a reason that the second repo was considered "more useful"? If so, it may be worth mentioning.

- logs: Logs.

### NODD - NOAA Open Data Dissemination Program
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With the smiley face removed, this bullet point no longer has a punchline, which means it actually needs to bear weight. What info is being logged in this folder?

(Granted, the logs folder linked currently contains nothing at all, logs or otherwise. Not sure whether the historical purpose of this folder needs to be mentioned, or if it can just be specified as empty.)

Coming soon: Big Query
#### Coming soon: Big Query

Efforts are underway to make some of the datasets from the NWM operational and retrospective simulations available on BigQuery for ultra-high-bandwidth access. Stay tuned...
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question: am I mistaken, or is this section outdated? I'm pretty sure BigQuery support for NWM retrospectives has been alive and well for some time, now.


Jupyter notebook instructions for processing NWM Zarr and NetCDF output formats [here](https://github.com/CIROH-UA/data_access_example/)

<details>

This comment was marked as resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants