We are looking to buy some new GPU nodes for the Argus Kubernetes cluster. Chris asked us to run some checks to find the cheapest type of GPU which is viable for running our desired program. We want to run AreTomo on these nodes because then we could scale the tomo_align service; at the moment we can only scale using the tomo_align_iris service, which doesn't have as high guarantees as Argus (and no SLA). AreTomo licensing was mentioned as a possible issue but I think this should be fine. Test A100 V100s - how to test in container? Mihai said to temporarily install Docker on Hopper - containerd, singularity is daemonless. Will it make a difference running in a Singularity container vs running directly on the node or in a Docker container? Chris says every system call is marshalled by the container process, so it could make a difference. Mihai seems to think it shouldn't make a difference. Run everything through Singularity containers. Take one node out to test - Hamilton? Test V100 on Argus Test A100 on Hopper/Hamilton Test other, lower spec GPUs on Pollux

Handover topics Deploying K8s stuff RMQ instances different repos current documentation cryoSPARC PRs to merge Stuff to pass on/do before I leave GPU benchmarking

https://www.bbc.co.uk/sport/football/world-cup/scores-fixtures Knockouts Final 16 Quarter-final Semi-final Final Netherlands vs USA (Kev vs Anna)

[ ] TEST https://github.com/DiamondLightSource/python-murfey/pull/82 [ ] GO training [ ] site pass and whiteboard fitting [ ] install Dave Farmer software https://github.com/juglab/cryoCARE_pip [ ] SynchWeb, JS .mrc viewer https://github.com/nglviewer/ngl [ ] permissions for k8s-em user [ ] mrc_out file path for remote rsync (relative) [ ] jenkins on K8s MotionCorr works!

(mc-feedback) [slg25752@ws466 murfey]$ murfey.server --feedback -e devrmq [09/02/22 12:50:54] INFO Starting Murfey RabbitMQ thread __init__.py:150 INFO Starting Murfey server version 0.5.10 for beamline m12, listening on 0.0.0.0:8000 __init__.py:154 INFO Started server process [3336154] server.py:82 INFO Waiting for application startup. on.py:45 INFO Application startup complete. on.py:59 INFO Uvicorn running on http://0.0.0.0:8000 (Press CTRL+C to quit) server.py:215 /scratch/slg25752/python-murfey/src/murfey/server/ispyb.py:178: SAWarning: relationship 'BLSession.BeamCalendar1' will copy column BeamCalendar.beamCalendarId to column BLSession.beamCalendarId, which conflicts with relationship(s): 'BLSession.BeamCalendar' (copies BeamCalendar.beamCalendarId to BLSession.beamCalendarId). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="BeamCalendar"' to the 'BLSession.BeamCalendar1' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx) db.query(BLSession) [09/02/22 12:50:57] INFO ('127.0.0.1', 33610) - "WebSocket /ws/test/21" [accepted] websockets_impl.py:218