pull commits from main to dev

[spearmangillman]

Script Organization

• Descriptive header (includes name, affiliation, date, brief description of script purpose)
• Parameters specified at top of script
• Files loaded at top of script
• Functions abstracted into separate script
• Organized into sections

Readability

• Repetitive code refactored into functions
• All functions have docstrings
• Descriptive in-line comments
• Correct casing for variables and functions: camelCase (R) or snake_case (Python)
• Descriptive variable and function names – variables should be nouns and functions should be verbs
• Used a linter

Generalizability

• No hardcoded values (all integers, strings, etc. should be specified at the top of the script in the “Parameters” section)
• Use relative file paths
• Consistent output file naming (e.g. “example-filename.tif”)

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Note

.coderabbit.yml has unrecognized properties

CodeRabbit is using all valid settings from your configuration. Unrecognized properties (listed below) have been ignored and may indicate typos or deprecated fields that can be removed.

⚠️ Parsing warnings (1)

Validation error: Unrecognized key(s) in object: 'code_guidelines', 'ai'

⚙️ Configuration instructions

• Please see the configuration documentation for more information.
• You can also validate your configuration using the online YAML validator.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch main

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}