Project-MONAI / Project-MONAI/MONAI
`properties_path` of `BundleWorkflow` only support json format
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.7k
- Forks
- 1.6k
- Avg merge
- 5d 1h
- Merged PRs (30d)
- 20
Description
It's different from the default setting: using a .py file to save properties:
https://github.com/Project-MONAI/MONAI/blob/684688a2877b07b0e1da98bb13f18a60ac73d426/monai/bundle/workflows.py#L51
For users that want to define a properties file, a simple way is to copy and modify the file: https://github.com/Project-MONAI/MONAI/blob/684688a2877b07b0e1da98bb13f18a60ac73d426/monai/bundle/properties.py
it's inconvenient to use json since it requires to manually "translate" ID_SEP_KEY, BundleProperty and BundlePropertyConfig.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading monai/bundle/workflows.py around the referenced BundleWorkflow configuration and compare it with monai/bundle/properties.py. Trace how properties_path is loaded and how the default Python properties file is represented. Done means users can provide a .py properties file without manually translating ID_SEP_KEY, BundleProperty, and BundlePropertyConfig into JSON.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json, python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100