Feature 1945 L0

[JohnHalleyGotway]

Pull Request Testing

• Describe testing already performed for these changes:
  
  None. I made the simple change and note that the NB output should remain unchanged. So I'm leveraging that automated testing instead of spending time testing manually.

• Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  
  Please just review the modified files.

• Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [Yes]
  
  I checked and the user's guide makes no mention of L0 vs Z0 for GO Index. No changes are needed.

• Do these changes include sufficient testing updates? [Yes]
  
  No additional testing is needed. The existing GO Index and SS Index jobs should both run and produce exactly the same output as before.

• Will this PR result in changes to the test suite? [No]
  
  If yes, describe the new output and/or changes to the existing output:
  

• Please complete this pull request review by [Wednesday 8/20/21].
  

Pull Request Checklist

See the METplus Workflow for details.

• Complete the PR definition above.
• Ensure the PR title matches the feature or bugfix branch name.
• Define the PR metadata, as permissions allow.
  Select: Reviewer(s)
  Select: Organization level software support Project or Repository level development cycle Project
  Select: Milestone as the version that will include these changes
• After submitting the PR, select Linked issues with the original issue number.
• After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
• Close the linked issue and delete your feature or bugfix branch from GitHub.

[michelleharrold]

@JohnHalleyGotway - I visually inspected the change from Z0 --> L0, and it looks good to me.