lincc-frameworks / lincc-frameworks/hyrax
Patch config for a different base directory
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 41
- Forks
- 7
- Avg merge
- 5d 1h
- Merged PRs (30d)
- 8
Description
**Feature request**
If the entire Hyrax project (inputs, outputs, configs) is moved elsewhere, the config becomes invalid. It would be useful to have functionality that updates the base directory for all paths in the config, e.g., `new_dir / path.relative_to(old_dir)` (assuming `pathlib.Path` objects).
**Before submitting**
Please check the following:
- [x] I have described the purpose of the suggested change, specifying what I need the enhancement to accomplish, i.e. what problem it solves.
- [ ] I have included any relevant links, screenshots, environment information, and data relevant to implementing the requested feature, as well as pseudocode for how I want to access the new functionality.
- [x] If I have ideas for how the new feature could be implemented, I have provided explanations and/or pseudocode and/or task lists for the steps.
Contributor guide
No contributing guide indexed for this repository
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
No file or test is named in the issue. Start by locating Hyrax's configuration and path-handling entry points, then trace how input, output, and config paths are represented. Done means exposing a way to relocate the base directory while preserving each path's relative location, with tests covering the moved configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100