ISISComputingGroup / ISISComputingGroup/IBEX

Reconsider the architecture for mini-insts/cut down instruments

Aperta
#7,451 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
Nessun dato sulla lingua
Stelle
6
Fork
2
Merge medio
16h 40m
PR unite (30g)
2

Descrizione

As someone wanting to use instantiations of IBEX which are less than the full server I want to clear up what the requirements, and come up with a plan to resolve this.

## Acceptance Criteria
- [ ] The various types of cut down IBEX setup are documented
- [ ] The documented use cases are then presented to the group and an architecture decision made on how to proceed
- [ ] Tickets are created to start enacting that decision

## Notes
- The last two points may need to be spun out into separate tickets
- This is not being added to the discussion list as there needs to be a better understanding of the use cases before the work can be undertaken
- Examples of systems which could benefit from not having to run a full IBEX server potentially: HIFI Cryomag; Triton PCs; Instron PC; HLM system; any remaining SECI instruments; CHIPIR
- #7450 may be useful in considering this architectural decision

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Direzione di ricerca

Start by reviewing the listed cut-down IBEX use cases, including HIFI Cryomag, Triton PCs, Instron PC, HLM, SECI instruments, and CHIPIR. Read issue #7450 for related context, then document the setup types and use cases; completion also requires presenting them for an architecture decision and creating follow-up tickets, unless those steps are split out.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Ambito
backend
Tipo di issue
Funzionalità
Difficoltà
5/5
Tempo stimato
Più di una settimana
Stato di attività
Ferma
Chiarezza
Abbastanza chiara
Idoneità per principianti
25/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.