[develop] S3 doc updates

[EdwardSnyder-NOAA]

DESCRIPTION OF CHANGES:

As part of the data governance initiative, all s3 buckets will need some sort of versioning control. To meet these needs the AWS S3 Bucket was reorganized with the develop data stored under a 'develop-date' folder and the verification sample case and the document case (current_release_data) moved under a new folder called 'experiment-user-cases'.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

TESTS CONDUCTED:

• hera.intel
• orion.intel
• hercules.intel
• cheyenne.intel
• cheyenne.gnu
• derecho.intel
• gaea.intel
• gaeac5.intel
• jet.intel
• wcoss2.intel
• NOAA Cloud (indicate which platform)
• Jenkins
• fundamental test suite
• comprehensive tests (specify which if a subset was used)

DEPENDENCIES:

DOCUMENTATION:

ISSUE:

CHECKLIST

• My code follows the style guidelines in the Contributor's Guide
• I have performed a self-review of my own code using the Code Reviewer's Guide
• I have commented my code, particularly in hard-to-understand areas
• My changes need updates to the documentation. I have made corresponding changes to the documentation
• My changes do not require updates to the documentation (explain).
• My changes generate no new warnings
• New and existing tests pass with my changes
• Any dependent changes have been merged and published

LABELS (optional):

A Code Manager needs to add the following labels to this PR:

• Work In Progress
• bug
• enhancement
• documentation
• release
• high priority
• run_ci
• run_we2e_fundamental_tests
• run_we2e_comprehensive_tests
• Needs Cheyenne test
• Needs Jet test
• Needs Hera test
• Needs Orion test
• help wanted

CONTRIBUTORS (optional):

[MichaelLueken]

@EdwardSnyder-NOAA -

It looks like the Indy-Severe-Data.tgz file has moved as well. It would be best to update .cicd/scripts/srw_metric.sh to use https://noaa-ufs-srw-pds.s3.amazonaws.com/experiment-user-cases/release-public-v2.1.0/METplus-vx-sample/Indy-Severe-Weather.tgz rather than https://noaa-ufs-srw-pds.s3.amazonaws.com/sample_cases/release-public-v2.1.0/Indy-Severe-Weather.tgz, which no longer exists.

Outside of this, these changes look good to me.

[MichaelLueken]

Thanks, @EdwardSnyder-NOAA, for modifying the srw_metric.sh script as well!

Approving now.

[EdwardSnyder-NOAA]

Thanks @MichaelLueken! Good catch with the srw_metric.sh script!

[MichaelLueken]

@EdwardSnyder-NOAA -

Further testing of the SRW metrics script suggests that it would probably be best to continue using the verification data from the release-public-v2.1.0 directory rather than the release-public-v2.2.0 verification data. Several changes would need to be made to the overall script in order to allow the release-public-v2.2.0 verification data to be read, just for stat_analysis not to compute a skill score in the end. For this reason, I suggest changing back to release-public-v2.1.0 for now while looking into the warning messages that are generated while attempting to run the metrics code using release-public-v2.2.0.

[MichaelLueken]

@EdwardSnyder-NOAA -

Thanks for making the modification to use the v2.1.0 verification data! Approving once again.

[RatkoVasic-NOAA]

Looks good to me.