prjemian
commented
3 weeks ago What about the catalog, should it be split?
This is a local choice. MongoDB can handle either way. That's what it is designed for.
- Will instruments be operated simultaneously? (You said yes)
- Will data from each instrument be fully separate, through analysis?
- Will multiple catalogs (one for each instrument) be difficult for the beam line support team?
- Can you apply metadata consistently to filter multiple instruments from a single catalog? (Probably can create a key that makes the distinction, so the question is how much of a challenge is it for users to filter on this key?)
That said, a single database means that searches can be more broad.
4idb, 4idg, 4idh, laser
The first three names are likely unique. laser is much too general given work at 7-ID and the PLD instrument that has been at 33-ID-D up until now. Might be others, as well. Probably best to make that one unique.
... multiple setups ...
The Deposition lab has this situation exactly. They renamed instrument to be one of their depo systems, then created copies for the other systems. Devices and plans common to all are in another directory they all share. Startup script parameters are used to run the depo system of choice. Your facility could follow a similar pattern.
gfabbris
In POLAR we could have 2-4 instruments running at the same time (4idb, 4idg, 4idh, laser). We currently have "Raman" and "instrument" setups, could do similarly for others, but, is this the best approach? What about the catalog, should it be split?