lincc-frameworks / lincc-frameworks/hyrax
Investigate collaboration with Hyrax across directory structures
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 41
- Forks
- 7
- Avg merge
- 5d 1h
- Merged PRs (30d)
- 8
Description
**Feature request**
We have 1 instance of someone trying to share output of a model to work on a different computing system. A large amount of directory structure is implicitly expected. Everything from the hard coded paths in the configuration files to the fact that when we create an instance of InferenceDataset, it attempts to spin up a hidden instance of the original dataset that references data in the original directories.
While it's only happened once so far, it's not an unreasonable request to think through.
Relates to issue #390
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
Start by reviewing related issue #390, the configuration files with hard-coded paths, and InferenceDataset. Trace how shared model output depends on the original dataset directories. Done means defining and implementing a collaboration approach that works across directory structures and computing systems without requiring the original paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100