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.

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

Consolidate Simulation Parameter Metadata into Core Library #300

Open
Atraxus opened this issue Jul 3, 2024 · 1 comment
Open

Consolidate Simulation Parameter Metadata into Core Library #300

Atraxus opened this issue Jul 3, 2024 · 1 comment
Assignees
Labels
A-core Area: The core library (rayx-core) A-ui Area: User interface for rendering and more C-enhancement Category: Adding a new feature

Comments

@Atraxus
Copy link
Collaborator

Atraxus commented Jul 3, 2024

To ensure that the necessary metadata for each parameter (such as range, human-readable labels, etc.) is available to the UI, we should centralize this data within the core library. This metadata is also crucial for parsing and model validation. By consolidating these definitions, we can avoid duplication, thereby reducing the risk of inconsistencies and outdated information.

@Atraxus Atraxus added C-enhancement Category: Adding a new feature A-ui Area: User interface for rendering and more A-core Area: The core library (rayx-core) labels Jul 3, 2024
@fannyzotter fannyzotter self-assigned this Jul 9, 2024
@fannyzotter
Copy link
Collaborator

A Database is a possible solution, but it should be local for each user. We would use SQLite.
As every Element has different Parameters this could be a Problem in a strict database model.
We could save whole Beamlines without xml or toml etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-core Area: The core library (rayx-core) A-ui Area: User interface for rendering and more C-enhancement Category: Adding a new feature
Projects
None yet
Development

No branches or pull requests

2 participants