Feature internal 46 logging

[ishita9]

Pull Request Testing

• Describe testing already performed for these changes:
  
  Unit tests to ensure that nothing breaks, SonarQube scan for code reliability and duplication, physically running agg_stat.py and other modules on seneca
• Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  
  Make sure the unit tests pass. Randomly run a few routines like agg_stat to look at the log statements. The log related entries can be made to the sample yaml files. Examples can be found under test directory.
• Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [Yes or No]
  Yes
• Do these changes include sufficient testing updates? [Yes or No]
  Yes
• Will this PR result in changes to the test suite? [Yes or No]
  
  If yes, describe the new output and/or changes to the existing output:
  
  Yes, log output will be generated under test_dir/logs
• Do these changes introduce new SonarQube findings? [Yes or No]
  
  If yes, please describe:
  No.
• Please complete this pull request review by [Fill in date].
  

Pull Request Checklist

See the METplus Workflow for details.

• Add any new Python packages to the METplus Components Python Requirements table.
• Review the source issue metadata (required labels, projects, and milestone).
• 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) and Development issue
  Select: Milestone as the version that will include these changes
  Select: Coordinated METplus-X.Y Support project for bugfix releases or METcalcpy-X.Y.Z Development project for official releases
• After submitting the PR, select the ⚙️ icon in the Development section of the right hand sidebar. Search for the issue that this PR will close and select it, if it is not already selected.
• 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.

[jprestop]

@bikegeek and @ishita9 Just wanted to ensure we were waiting for @lisagoodrich to finish up the documentation before approving this request. There is a problem with the documentation - I know what it is I just haven't gotten to it yet (just fyi).

[ishita9]

Oh yes! Lisa needs to finish her part. Thanks -Ishita

…

On Tue, Oct 1, 2024 at 4:22 PM Julie Prestopnik ***@***.***> wrote: @bikegeek <https://github.com/bikegeek> and @ishita9 <https://github.com/ishita9> Just wanted to ensure we were waiting for @lisagoodrich <https://github.com/lisagoodrich> to finish up the documentation before approving this request. There is a problem with the documentation - I know what it is I just haven't gotten to it yet (just fyi). — Reply to this email directly, view it on GitHub <#400 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIYROXGXPVKMDMK27TVGDA3ZZMVCNAVCNFSM6AAAAABPGR5YXGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBXGI2TCOBYGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[lisagoodrich]

Help!!! @bikegeek I'm not finished yet. I have 2 more pages of documentation to add on feature_46_internal_46_logging branch. Is that okay?

[bikegeek]

That is OK, I haven't closed the issue yet. Let me know when everything is ready to go. Thanks for working on the documentation.

…

On Wed, Oct 2, 2024 at 12:58 PM lisagoodrich ***@***.***> wrote: Help!!! @bikegeek <https://github.com/bikegeek> I'm not finished yet. I have 2 more pages of documentation to add on feature_46_internal_46_logging branch. Is that okay? — Reply to this email directly, view it on GitHub <#400 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA4UJHWKJ3DDOZPU3BSOI7TZZQ65FAVCNFSM6AAAAABPGR5YXGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBZGQ3TANBRGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>