Skip to content
This repository was archived by the owner on Jun 7, 2021. It is now read-only.
This repository was archived by the owner on Jun 7, 2021. It is now read-only.

Naming Convention for Lattice Files #16

@jbengtsson

Description

@jbengtsson

For a lattice design project, i.e., covering the evolution from a:

design concept -> CDR -> PDR -> etc.

given the multitude of lattice files that will be generated during this activity – and exchanged between individuals & groups, i.e., the End Users – a well thought out naming convention at the outset, is as important as e.g. ditto for the parameters for a control system for such a system:

<system> -> <sub-system> -> <sub-sub-system> -> etc.

Hence, for a Straw Man proposal for Functional Specs – i.e., What vs. How/Design Specs – I suggest:

<accelerator> <engineering footprint/structure> <linear optics> <nonlinear dynamics> <version>

.

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