Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Introduce workspace manifests #102

Open
integraledelebesgue opened this issue Jan 8, 2025 · 0 comments
Open

Introduce workspace manifests #102

integraledelebesgue opened this issue Jan 8, 2025 · 0 comments
Labels
architecture An issue related to the general design and mutual relations between the parts of the project feature New feature or request framework A general, framework-related topic

Comments

@integraledelebesgue
Copy link
Member

integraledelebesgue commented Jan 8, 2025 •
edited
Loading

Rationale

The following functionalities require some structured, formal configuration:

  • Model paths for Estimators - #86
  • Parameter presets for Estimators
  • AruDice rigid models - #92
  • Calibration and transformation presets

Idea

Every workspace should have a configuration file (preferably in the TOML format).

It should contain:

  • Paths to files containing weights for ML models
  • Optional constant parameters for particular Estimators
  • Optional paths to calibration and transformation presets (overriding the default location in the workspace)
  • Generic settings used during processing (e.g. torch.device)
@integraledelebesgue integraledelebesgue converted this from a draft issue Jan 8, 2025
@integraledelebesgue integraledelebesgue added feature New feature or request framework A general, framework-related topic labels Jan 8, 2025
@integraledelebesgue integraledelebesgue mentioned this issue Jan 8, 2025
Open
@integraledelebesgue integraledelebesgue marked this as a duplicate of #93 Jan 8, 2025
@integraledelebesgue integraledelebesgue added the architecture An issue related to the general design and mutual relations between the parts of the project label Jan 8, 2025
@integraledelebesgue integraledelebesgue moved this from Backlog to TODO in ChildLab Framework Jan 8, 2025
@integraledelebesgue integraledelebesgue marked this as not a duplicate of #93 Jan 20, 2025
@integraledelebesgue integraledelebesgue moved this from TODO to Backlog in ChildLab Framework Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
architecture An issue related to the general design and mutual relations between the parts of the project feature New feature or request framework A general, framework-related topic
Projects
ChildLab Framework
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@integraledelebesgue