Don't quote me on this because I only covered the topic briefly in some applied classes before doing 6 years of research, but if I remember correctly, you grab it with long tweezers and dump it in a shielded "garbage can" type container. And fill tons of paperwork that involves estimating the radiation dose delivered to everyone that could've been exposed. And probably present a post mortem at conferences about how you dealt with it.
It's much more primitive than you think. Dose distributions are simulated based on a CT/MRI that was acquired before treatment (treatment often lasts weeks). Only minor corrections are made when anatomy changes during the course of treatment, even though the patient is often losing tons of weight due to chemo, etc. There are quite a few tools that help with patient positioning, like vac-lok bags or literally molding a mask and drilling it down on the treatment couch (an example is shown here: https://newsnetwork.mayoclinic.org/discussion/new-radiothera...).
Motion during treatment can be tracked with cameras or IR sensors or subcutaneous probes but that doesn't tell you about internal organs moving. The topic of deformable registration, where you find a non-rigid mapping between initial imaging conditions and the current ones, is still a topic of active research. Adaptive planning, where you actively change the treatment plan every N sessions based on the most up to date information, is also actively researched / implemented in some good research centers.
For treatment planning you just use a standard Cartesian grid, or a "beam's eye view" coordinate system that's aligned with the radiation beam axis as it rotates around the patient.
Just defended my PhD thesis in medical physics. Worked on radiation therapy treatment planning, which combines optimisation theory with the physics of Monte Carlo particle transport engines (and more macro energy deposition modeling as well) to simulate millions of different radiation dose distributions in patients and figure out which combination will lead to the right outcome based on what the radiation oncologist prescribes.
People in my field are fairly fortunate as there is a career track as a clinical medical physicist that is highly paid and pretty low stress, so most people end up going there. The work consists of maintaining and calibrating the radiation therapy machines, along with implementing new technologies in the clinic, and fixing problems that don't fall within the job description of the radiation therapists. Like what to do when a radioactive seed falls on the floor instead of going inside the patient where it's supposed to go. There's also a separate track as an imaging physicist where you maintain and QA the diagnostic imaging machines.
I'm personally doing a postdoc at the junction between optimisation, machine learning and radiation therapy. Just starting out though. Basically just extending my PhD work to automate the treatment planning process and remove the variability in treatment plan quality due to the level of experience of the people making the plans.
I want to echo point #2 about listening rather than talking. When I first pitched my work to radiation therapy vendors at big conferences, I was expecting a kind of adversarial exchange to take place where I'd have to defend my software against cynical people trying to find its flaws, shark-tank style.
Instead I found that vendors were dying to tell me what they need and what's important for them. I quickly realised that the most important part after giving my pitch was to basically ask tons of questions about what they think is important and why. The vendors' answers were invaluable in honing my pitch for other vendors, but also to steer the direction of my project.
-Working for a big tech company: you're writing code to deliver more ads to more people so the company can grow and deliver even more ads to even more people
-Being a truck driver: you're moving boxes around
-Being a professional hockey player: you and your team are moving really fast with a disk shaped object trying to put it in a net while people try to prevent you from doing it
-Being a stock trader: making money by spending your whole life reading company reports and hoping you're right about whether they're doing well or not
-Being a quant: using your hard earned computer science skills to move money around and turn a profit instead of helping humanity
Almost every human endeavor can be trivialized if you choose to only see one side of it.
I wish MUDs were featured more prominently in online gaming history. They basically defined my childhood, and I learned how to code by writing vendor bots on a MUD. Dealing with edge cases (customers trying to buy invisible items without being able to see invisible!) and people trying to scam my bots taught me some valuable programming lessons that stick with me to this day.
In general, the field is split into imaging research (MRI, CT, Ultrasound, optical imaging) and radiotherapy research. It's a very applied field, the fundamental physics has been figured out a long time ago except for some really niche areas. For example, some people are trying to model particle transport inside DNA itself at the nanometer scale, where the transported particles have very low energies. There's still some physics work to be done there, but it's pretty marginal and the lack of theory in those areas is mostly due to theoretical physicists losing interest rather than the theory being too difficult.
I personally work in radiotherapy, making simplified (faster) Monte Carlo particle transport algorithms for use in treatment planning, and also finding more "modern" optimisation techniques to handle the many degrees of freedom available on radiotherapy linear accelerators to produce higher quality treatment plans compared to what we can do right now. It's hard to define what a high quality treatment plan is without a lot of background, but basically we try to find ways to put more radiation in tumours while sparing the healthy tissue all around the tumour. My "research" is like 95% programming.
I've had a similar experience. I'm in a hybrid field (medical physics) where half of the people are from pure physics and the other half from a more biomedical engineering background.
It's pretty funny to see the culture clash between the two when it comes to writing articles. We had to learn latex in our first year of undergrad to write lab reports whereas the biomed people really don't see any value in using latex over word (especially for collaborating).
He published a single author paper even though he acknowledges in the end "I thank Matthew Fiedler, PhD, and Jeanne Lambrew, PhD, who assisted with planning, writing, and data analysis". In my field, those people probably would have deserved a place on the authors list ;)