Skip to content

docs: add shabnam to developer notes #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 23, 2025
Merged

docs: add shabnam to developer notes #12

merged 2 commits into from
May 23, 2025

Conversation

ShbnmTjk
Copy link
Contributor

@ShbnmTjk ShbnmTjk commented May 22, 2025

Summary by CodeRabbit

  • New Features
    • Added a new radiomics feature extraction configuration for original and wavelet image types.
  • Documentation
    • Introduced separate developer notes for Katy and Shabnam, each with detailed tracking and project information.
    • Updated documentation navigation to provide direct access to individual developer notes.

Copy link
Contributor

coderabbitai bot commented May 22, 2025

"""

Walkthrough

This update adds a new radiomics feature extraction configuration YAML file, introduces detailed developer notes for two contributors, and restructures the documentation navigation to separate these notes. It includes new documentation files, an updated navigation configuration, and a new radiomics extraction settings file.

Changes

File(s) Change Summary
config/pyradiomics/aerts_original_wavelet.yaml Added a YAML configuration for radiomics feature extraction specifying image types (Original, Wavelet), feature classes, and settings (binWidth, resampledPixelSpacing).
docs/devnotes/.pages Added navigation configuration listing katy_notes.md and shabnam_notes.md to define documentation order.
docs/devnotes/katy_notes.md, docs/devnotes/shabnam_notes.md Added developer notes tracking radiomics feature extraction status, project structure, manuscript preparation tasks, and dataset management.
mkdocs.yaml Updated navigation: replaced single "Developer Notes" entry with separate "Katy's Notes" and "Shabnam's Notes" entries for clearer documentation structure.

Possibly related PRs

Poem

In burrows deep, two notes appear,
Katy and Shabnam’s voices clear.
A YAML config hops in place,
With features, shapes, and pixel space.
Docs now split for every bunny,
Radiomics work—oh, isn’t it funny?
🥕✨
"""

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 71eeda9 and 0e35b46.

📒 Files selected for processing (1)
  • mkdocs.yaml (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • mkdocs.yaml

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • 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

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (8)
config/pyradiomics/aerts_original_wavelet.yaml (1)

15-15: Add a newline at end-of-file.
YAML files should end with a single newline to satisfy linter rules and avoid warnings.

🧰 Tools
🪛 YAMLlint (1.37.1)

[error] 15-15: no new line character at the end of file

(new-line-at-end-of-file)

docs/devnotes/shabnam_notes.md (2)

6-6: Use consistent heading levels.
You're jumping from an H1 (# Developer Notes) directly to an H4 (#### [2025-05-20] ...). Use H2 or H3 for this subsection:

- #### [2025-05-20] Tracking extraction of all features for Aerts signature
+ ## [2025-05-20] Tracking extraction of all features for Aerts signature
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

6-6: Heading levels should only increment by one level at a time
Expected: h2; Actual: h4

(MD001, heading-increment)


17-17: Add a comma for readability.
Insert a comma after "config file" to improve sentence flow:

- I think the paths in the run readii should be passed in a config file since I can't run two datasets at the same time.
+ I think the paths in the run readii should be passed in a config file, since I can't run two datasets at the same time.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~17-~17: Possible missing comma found.
Context: ...run readii should be passed in a config file since I can't run two datasets at the s...

(AI_HYDRA_LEO_MISSING_COMMA)

docs/devnotes/katy_notes.md (5)

4-4: Normalize heading increments.
You have an H1 (# Developer Notes) followed by an H4 (#### [2025-05-05] ...). Use H2 or H3 for these date-stamped sections:

- #### [2025-05-05] PyRadiomics original_all_features extraction tracking
+ ## [2025-05-05] PyRadiomics original_all_features extraction tracking
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

4-4: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4

(MD001, heading-increment)


28-28: Convert bare URL to a Markdown link.
Replace the plain URL with a hyperlink to conform to lint rules:

- * Bootstrapping help came from: https://acclab.github.io/bootstrap-confidence-intervals.html
+ * Bootstrapping help came from: [Bootstrap Confidence Intervals](https://acclab.github.io/bootstrap-confidence-intervals.html)
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

28-28: Bare URL used
null

(MD034, no-bare-urls)


35-36: Fix nested list indentation.
Nested items under "Since RADCURE was processed..." should be indented by two spaces, not four:

-     * Change the column `patient_ID` to `PatientID`
-     * Add index column label `SampleID`
+   * Change the column `patient_ID` to `PatientID`
+   * Add index column label `SampleID`
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

35-35: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


36-36: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


49-49: Adjust heading level for manuscript feedback section.
Under "## Manuscript Notes", the date-stamped section should be H3, not H4:

- #### [2025-05-14] Manuscript Review Feedback Notes
+ ### [2025-05-14] Manuscript Review Feedback Notes
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

49-49: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4

(MD001, heading-increment)


51-51: Replace emphasized section titles with proper headings.
Use Markdown headings instead of bold text for section names:

- **Introduction/Background**
+ ### Introduction/Background

- **Methods**
+ ### Methods

- **Results**
+ ### Results

- *Plots*
+ ### Plots

Also applies to: 56-56, 67-67, 81-81

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

51-51: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 50975f1 and 71eeda9.

📒 Files selected for processing (5)
  • config/pyradiomics/aerts_original_wavelet.yaml (1 hunks)
  • docs/devnotes/.pages (1 hunks)
  • docs/devnotes/katy_notes.md (1 hunks)
  • docs/devnotes/shabnam_notes.md (1 hunks)
  • mkdocs.yaml (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
docs/devnotes/katy_notes.md

4-4: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4

(MD001, heading-increment)


28-28: Bare URL used
null

(MD034, no-bare-urls)


35-35: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


36-36: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


49-49: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4

(MD001, heading-increment)


51-51: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)


53-53: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


54-54: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


56-56: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)


58-58: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


59-59: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


60-60: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


61-61: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


62-62: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


63-63: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


64-64: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


67-67: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)


69-69: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


70-70: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


71-71: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


72-72: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


73-73: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


74-74: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


75-75: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


76-76: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


77-77: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


78-78: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


79-79: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


81-81: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)


83-83: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


88-88: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4

(MD001, heading-increment)

docs/devnotes/shabnam_notes.md

6-6: Heading levels should only increment by one level at a time
Expected: h2; Actual: h4

(MD001, heading-increment)

🪛 LanguageTool
docs/devnotes/shabnam_notes.md

[uncategorized] ~17-~17: Possible missing comma found.
Context: ...run readii should be passed in a config file since I can't run two datasets at the s...

(AI_HYDRA_LEO_MISSING_COMMA)

🪛 YAMLlint (1.37.1)
config/pyradiomics/aerts_original_wavelet.yaml

[error] 15-15: no new line character at the end of file

(new-line-at-end-of-file)

🔇 Additional comments (1)
docs/devnotes/.pages (1)

1-3: Navigation entries look correct.
The order and filenames correspond to the newly added developer notes files.

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
@strixy16 strixy16 merged commit 8794a51 into main May 23, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants