Is your feature request related to a problem? Please describe.
The sequences are effectively an experimental artifact now that they are used to run experiments repeatably and consistently. They should be stored somewhere independently of a development-focused view like this repo's.
Describe the solution you'd like
A repository for sequences should be created. This can be installed into the aixi_campaigns repo and the sequences updated from there, making it easy to maintain traceability for them. It's a simple configuration option to read the sequences from somewhere else on the livex.cfg side.
Describe alternatives you've considered
They could continue to be committed to the repo and updated and moved manually. But it would be easier somewhere else.
Additional context
This will become more important as sequencer understanding and later mastery by users increases.
Is your feature request related to a problem? Please describe.
The sequences are effectively an experimental artifact now that they are used to run experiments repeatably and consistently. They should be stored somewhere independently of a development-focused view like this repo's.
Describe the solution you'd like
A repository for sequences should be created. This can be installed into the aixi_campaigns repo and the sequences updated from there, making it easy to maintain traceability for them. It's a simple configuration option to read the sequences from somewhere else on the livex.cfg side.
Describe alternatives you've considered
They could continue to be committed to the repo and updated and moved manually. But it would be easier somewhere else.
Additional context
This will become more important as sequencer understanding and later mastery by users increases.