List of microscopes
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- authentication, backend
Research direction
Start by locating smartem_backend and its existing authentication or microscope-related entry points, then review how the /admin frontend and smartem_agents might consume the list. Confirm the named microscope-to-id mappings against the issue and make the list available for recognition and administrative use; document any remaining source-of-truth limitation involving UAS or ISPyB.
Written by the indexing model from the issue text.
Description
Encode the list of microscope as a hardcode in smartem_backend initially, to be updated by hand, then look at better ways of doing it. This may be useful for authenticating smartem_agents (do we recognise this microscope) and potentially for /admin route in the f/e
This is the list:
- Krios 1 - m02
- Krios 2 - m03
- Talos - m04
- Scios - m05
- Krios 3 - m06
- Krios 4 - m07
- Krios 5 - m08
- Glacios 1 - m10
- Aquilos - m11
- Glacios 2 - m12
- Leica cryoCLEM - m14
the true source of truth is UAS which we don’t have programmatic access to. it’s the user administration system. it’s how users apply for beam time and see what is scheduled. uas.diamond.ac.uk. it’s separated from other systems so a bunch of the information in there ends up being mirrored in ISPyB (https://github.com/DiamondLightSource/ispyb-database) which is what we use as the source of truth for sessions and what instrument they’re booked on. Guilherme de Freitas may have ideas on how to get this list programatically.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DiamondLightSource/smartem-devtools
-
security
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Dependency Dashboard Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
research security
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
devops research smartem-agent
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
enhancement smartem-devtools:claude
Difficulty 5/5 Over a week Newbie friendliness 45/100
All issues in DiamondLightSource/smartem-devtools
Similar issues
-
VerificationGate: ATTRIBUTION quote guard never matches a normal quotation (\b around the quote) Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
danielmiessler/LifeOS#2234 ·
-
T: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Mend: dependency security vulnerability untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 70/100