removing mkObj from codebase

[MOshima-PIFSC]

What is the feature?

• Removed mkObj() from codebase because the function was no longer used

How have you implemented the solution?

I removed the the script with the function (io.R) and ran devtools::document() to remove man/mkObj.Rd, and removed the function from the namespace.

Does the PR impact any other area of the project?

None

How to test this change

I ran devtools::check() and the changes did not cause any errors.

Developer pre-PR checklist

• [x] I relied on GitHub actions to :test_tube: things for me while I sat on the :couch_and_lamp:.

[github-actions[bot]]

Instructions for code reviewer

Hello reviewer, thanks for taking the time to review this PR!

• Please use this checklist during your review, checking off items that you have verified are complete!
• For PRs that don't make changes to code (e.g., changes to README.md or Github actions workflows), feel free to skip over items on the checklist that are not relevant. Remember it is still important to do a thorough review.
• Then, comment on the pull request with your review indicating where you have questions or changes need to be made before merging.
• Remember to review every line of code you’ve been asked to review, look at the context, make sure you’re improving code health, and compliment developers on good things that they do.
• PR reviews are a great way to learn, so feel free to share your tips and tricks. However, for optional changes (i.e., not required for merging), please include nit: (for nitpicking) before making the suggestion. For example, nit: I prefer using a data.frame() instead of a matrix because...
• Engage with the developer when they respond to comments and check off additional boxes as they become complete so the PR can be merged in when all the tasks are fulfilled. Make it clear when this has been reached by commenting on the PR with something like This PR is now ready to be merged, no changes needed.

Checklist

• [ ] The PR is requested to be merged into the appropriate branch (typically main)
• [ ] The code is well-designed.
• [ ] The functionality is good for the users of the code.
• [ ] Any User Interface changes are sensible and look good.
• [ ] The code isn’t more complex than it needs to be.
• [ ] Code coverage remains high, indicating the new code is tested.
• [ ] The developer used clear names for everything.
• [ ] Comments are clear and useful, and mostly explain why instead of what.
• [ ] Code is appropriately documented (doxygen and roxygen).

[MOshima-PIFSC]

@Andrea-Havron-NOAA I made the changes you requested and now it is passing all tests!

[Andrea-Havron-NOAA]

looks good!