Ehancement to kaapana_ivim_osipi

[Unique-Usman]

• Thorough Testing of each of the Algorithms available through using the new Workflows.
• Dynamically populating the "Segmentation Algorithm" in the UI form instead of Hardcoding https://github.com/OSIPI/TF2.4_IVIM-MRI_CodeCollection/blob/main/kaapana_ivim_osipi/ivim-fitting-method/extension/docker/files/dag_ivim-fitting_method.py#L49C27-L49C49
• Merging together nifti_wrapper.py and nifti_wrapper_kaapana.py in https://github.com/OSIPI/TF2.4_IVIM-MRI_CodeCollection/tree/main/WrapImage
• Merging Together https://github.com/OSIPI/TF2.4_IVIM-MRI_CodeCollection/blob/main/Docker/Dockerfile and https://github.com/OSIPI/TF2.4_IVIM-MRI_CodeCollection/blob/main/kaapana_ivim_osipi/ivim-fitting-method/processing-containers/ivim-fitting-method/Dockerfile
• Setting up the workflow from scratch to ensure it works.

[rohitx01]

@Unique-Usman Hi, is this Issue still open for contributions? I would love to get involved.
I have over 2 years of experience in JavaScript (Full Stack) and Python, with notable work on client-based projects for Walmart and Google Partners.
I’m eager to contribute to open source, and OSIPI’s mission resonates deeply with me on a personal level. I would truly appreciate it if you could consider me.
Thank you!

[Unique-Usman]

Hello @rohitx01,

Glad that you are interested in getting involved.

Yeah, the above is open to contribuions.

But, I will say you will need to look into this pr -> #112 before you will be able to make any enhance to kaapana_ivim_osipi. The pr was the one that introduce it. What matter most is going through the readme introduce by the pr and see if you can replicate it on your machine.

If you are able to do that, then the other tasks will become easy to tackle.

If you have any questions or face any problem, do let me know.

[rohitx01]

Hi @Unique-Usman,

Thank you for accepting my request and yes, I'm interested in contributing to Issue #115.

I've forked the repo and reviewed the documentation, but I've run into a practical constraint: my local hardware (16GB RAM max) falls short of Kaapana's documented 64GB minimum RAM requirement for Task #5 (fresh installation testing).

I have a few options to move forward:

1. Spin up a GCP VM meeting the specs - I have ~2 years of experience with GCP infrastructure, Docker, and CI/CD pipelines from my day job
2. Request access to a development Kaapana instance if you have one available for testing
3. Focus on tasks number updated git instructions #2-4 first (algorithm dropdown automation, wrapper/Dockerfile consolidation) - these can be done locally without the full platform deployment

Which approach would be most valuable for the project right now?

PS: I could make meaningful progress on Tasks #2-4 locally (code changes, Docker builds, unit tests) but would need either:

• Access to test instance for integration testing, OR
• Submit PRs and rely on maintainer testing in your environment

Task #4 (Dockerfile merge) seems most feasible since I can test Docker builds locally. Would that be a good starting point?

Looking forward to contributing!

[Unique-Usman]

Hello @rohitx01,

Sorry for late reply,

While the Minimum requirement is 64GB RAM, if you have access to a remote server with less, you should be able to install it meanwhile, the minimum recommendation will ensure it works well.

Answering each of you questions:

1. Yeah, if you have access to one it will be very good.
2. I am not sure if the one we used for development is still up, I will have to ask.
3. Yeah, you can start with that but, before it can be accepted, we will still need to test it.

Apparently combining the two docker is a good start but, retireiterating on my point we will still need to test it works. The second one is also a good start.

I will check if the deployement server is still up. You can also check other issue which might not require setting up kaapana.

[rohitx01]

Hi @Unique-Usman,

Thanks for clarifying! Since I don't have access to a remote server at the
moment, I'll start with Task #4 (Dockerfile merge) as that's fully
testable locally with Docker Desktop.

My plan:

1. Consolidate the two Dockerfiles using build arguments
2. Test both build scenarios locally
3. Document what I tested vs. what needs Kaapana verification
4. Submit a PR for review

I'll also check out other issues in the repo that don't require Kaapana
as you suggested.

Should have an initial PR ready in the next few days!

Thanks!

[Unique-Usman]

Yeah, best of luck.

[rohitx01]

Hi @Unique-Usman,

I've completed Task #4 (Dockerfile Merge) and submitted PR #127

Summary

• Created unified Dockerfile.unified consolidating both Standalone and Kaapana Dockerfiles
• Successfully tested both build scenarios locally:
• Standalone: 13.2GB image (ID: 75a626d42f0b)
• Kaapana: 14GB image (ID: f662fb55bfee)
• Added build scripts and comprehensive documentation

Build Arguments

• BASE_IMAGE - Configure base Docker image
• ENV_TYPE - Choose between standalone or kaapana

Testing

Local testing completed with Docker Desktop on Windows. Integration testing in actual Kaapana environment required.

Next Steps

I'm ready to work on Task #2 (Dynamic Algorithm Dropdown) while you review this PR.

Looking forward to your feedback!

Thanks,
Rohit

[Unique-Usman]

Hello @rohitx01,

Whenever I do not reply with two days, do ping me.

I will check the PR.

[rohitx01]

Hi @Unique-Usman , sure ill ping you from next time. But I would appreciate , if you can review the current PR once, as it was my first here, so incase I am doing something wrong, I will keep in mind for the remaining issues, and incase I have done it correctly, I will start with remaining ones.

[oliverchampion]

is this finished now?