Skip to content

Consider a way to enforce naming conventions in optimas script #287

@RemiLehe

Description

@RemiLehe

The simulations script cannot use the simulation names from the configuration file directly (e.g. Laser energy [J]: see here) and instead have to use names that satisfy the Jinja2 constraints (e.g. laser_energy: see here and here).

As of #190, we additionally require that the names used in the simulation script are derived from the names in the configuration file, in a specific way:
https://github.com/BLAST-AI-ML/synapse/blob/main/dashboard/calibration_manager.py#L32

We should think how this could be enforced and/or how to document it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions