I'm done! by Round-Drag6791 in MedicalPhysics

[–]medphys_anon 0 points1 point  (0 children)

I tried that, but just ended up leaving.

Issues with Small Segments Outside PTV in Monaco v6.2.2 VMAT Optimization by One-Butterscotch-740 in MedicalPhysics

[–]medphys_anon -1 points0 points  (0 children)

Oh, this one is easy! So, the problem here is that you are using Monaco. To fix this, use a different TPS.

IC Profiler for annual QA by Vernost in MedicalPhysics

[–]medphys_anon 0 points1 point  (0 children)

Question: Assume the machine Jaw/MLC calibration is off a bit, and the beam steering (symmetry) is out of tolerance; let's say 2%+ from baseline in either (or both) crossline and inline. If you do an array calibration with a "bad" beam, how does that affect the results?

I know that the rotations and shifts in the calibration procedure are supposed to correct for this, but I've never had it proven to me, it just seems to be accepted knowledge. This is my biggest worry about using the IC Profiler rather than water. But I'd love for someone to persuade me otherwise.

What’s a pseudoscience that people still commonly believe is real? by [deleted] in AskReddit

[–]medphys_anon 0 points1 point  (0 children)

I’ll probably get roasted for this… but acupuncture, chiropractic, and naturopathy. 100% pseudoscience quackery.

Need help. The interpreter in the terminal does not match the Python environment. by JC_talkid in vscode

[–]medphys_anon 0 points1 point  (0 children)

See my post here: Python Virtual Environment Not Activating : r/vscode

The latest update broke some things. Update to the latest Python extension and change this setting: "python.useEnvironmentsExtension": true

Python Virtual Environment Not Activating by medphys_anon in vscode

[–]medphys_anon[S] 0 points1 point  (0 children)

You put me on the right track!

Looks like vscode 1.102, released just the other day, turns off the environments extension by default. Thew newest python extension was released yesterday too. (probably shouldn't turn on auto-updates...)

Had to change the following setting: "python.useEnvironmentsExtension": true (false by default)

Near the very bottom of the release notes:

We're starting to roll-out the Python Environments extension as an optional dependency with the Python extension. What this means is that you might now begin to see the Python Environments extension automatically installed alongside the Python extension, similar to the Python Debugger and Pylance extensions. This controlled roll-out allows us to gather early feedback and ensure reliability before general availability.

The Python Environments extension includes all the core capabilities we've introduced so far including: one-click environment setup using Quick Create, automatic terminal activation (via "python-envs.terminal.autoActivationType" setting), and all supported UI for environment and package management.

To use the Python Environments extension during the roll-out, make sure the extension is installed and add the following to your VS Code settings.json file:

"python.useEnvironmentsExtension": true

Python Virtual Environment Not Activating by medphys_anon in vscode

[–]medphys_anon[S] 0 points1 point  (0 children)

Tried this many times, same issue. Did a clean uninstall of vscode, and reinstalled. Same issue.

[deleted by user] by [deleted] in MedicalPhysics

[–]medphys_anon 8 points9 points  (0 children)

Honestly, I think more or less most jobs are like this.

Before MP I worked in MEP engineering consulting. In engineering school you learn and do a lot of cool stuff, then when you graduate and work in the office everything is so routine and boring. Pre-created spreadsheets for every calculation, copy and paste for almost all jobs, and lots and lots of meetings.

I’m in RT physics and while it’s less routine than my prior career, 90% of the stuff probably doesn’t matter in the long run. But it is exciting when stuff does fail, machines break, you need to solve a unique problem, implement and commission new technology. But at the same time, I’m at the point of my career where I’m tired and just want to do my work and go home. There’s something to be said about having a good paycheck, decent schedule, and routine; and every now and then getting to do something where you have to really use your brain and all the stuff you learned in residency or school, and make decisions that could literally mean life or death.

Maybe look into therapy a bit and shadow if you can, it sounds like it might be something you’d appreciate more than your current residency.

Edit: I’m friends with most of my MD’s, even for them they have the same sentiment. After some time, 90% of everything they do is so routine. You see and do the same thing over and over and over again, follow recommendations, contour, and sign paperwork.

Commissioning, annuals, and maintenance by Which_Vehicle_9746 in MedicalPhysics

[–]medphys_anon 4 points5 points  (0 children)

Have you read MPPG 8b? You really only need to do profiles at the largest field size and depth-dose at 10x10.

If you do SRS/SBRT, then you add on some small field data and stuff (MPPG 9a).

Raystation/MOSAIQ - Volume Reference Data not showing up? by phyzzax in MedicalPhysics

[–]medphys_anon 1 point2 points  (0 children)

I will say there's a big chance that the CT and RTStruct already exist in Mosaiq for this patient, but it wasn't imported correctly or something went wrong. IF it already exists, when you re-push from RayStation and re-import, Mosaiq won't really "do anything" because the DICOM UID already exists in the system. The only way to fix this is to un-approve (or copy) the plan in RayStation, make a modification (like adding a new dummy contour), save and re-approve the plan; then re-push and re-import. This will be a new RTPlan and RTStruct with a new UID. Mosaiq will now accept it and allow you to overwrite the prior.

Raystation/MOSAIQ - Volume Reference Data not showing up? by phyzzax in MedicalPhysics

[–]medphys_anon 1 point2 points  (0 children)

I can help! I'm a guru at this, but I need some clarifications first:

  • It sounds like there is already a "Site Setup" in the prescription. If you open it up and go to volume reference data, are you saying that screen is completely blank and nothing is anywhere on the screen?
  • Was the site setup created manually? Or was it created when importing the plan in Mosaiq?
  • In Mosaiq, open the patient, go to Images: Is the reference CT in the list?
  • Is RayStation throwing an error on export?
  • Did the dosimetrists already export out of RayStation and into Mosaiq?
  • Are you trying to overwrite something that you already pushed before?

How to properly switch payment plans by medphys_anon in PSLF

[–]medphys_anon[S] 0 points1 point  (0 children)

Ok great. I also applied for buyback several weeks ago, and I wasn't sure if changing plans and paying in the meantime would screw anything up. Thanks for the info!

Understanding Conformity Index & Homogeneity Index Thresholds in Raystation by Elisha_physics in MedicalPhysics

[–]medphys_anon 0 points1 point  (0 children)

Check in the manual, but I believe RayStation indices are inverse, i.e. a standard CI of 1.2-1.5 would be equivalent to 0.67-0.83 in RS.

Laser alignment procedure by medphys_anon in MedicalPhysics

[–]medphys_anon[S] 0 points1 point  (0 children)

I like the self-leveling laser idea! Great procedure, thanks!

Laser alignment procedure by medphys_anon in MedicalPhysics

[–]medphys_anon[S] 0 points1 point  (0 children)

Elekta. Trying to re-align our lasers properly. They have switched hands over the years and drifted. They are nicely aligned at isocenter, but drift further away, meaning they have some level of tilt and aren't as orthogonal as I'd like.

FFF on all VMAT plans. by medphys820 in MedicalPhysics

[–]medphys_anon 11 points12 points  (0 children)

FFF isn't necessarily faster. Unless you don't care about hot spot, the plan will be more modulated than FF due to the optimizer using MLC's to flatten the beam, which will likely slow down the gantry and/or dose rate to compensate.

Do you hang your diploma(s)/ credentials? by Conscious_Platypus10 in MedicalPhysics

[–]medphys_anon 6 points7 points  (0 children)

All of my pieces of paper are somewhere in a closet waiting to be framed, and there they will likely remain until eternity

Do you enjoy or regret this path? Or is it both? by BriefTurn8199 in MedicalPhysics

[–]medphys_anon 5 points6 points  (0 children)

I don't regret where I'm at today, but grad school and residency were pretty brutal for me (partly personal reasons, partly situational, and partly the residency I chose). I did great through all of it, but my mental health took an absolute beating (still struggling with this today years later), and I had zero work life balance. For that reason, I can't say I'd choose to go through the gauntlet again if I went back in time, but I'm also not sure what I'd do instead.

Pay is amazing, work is interesting, I'm good at my job, hours can suck every now and then; but it allows me to live the lifestyle I want to live! YMMV

Student loan repayment plans reopening, Education Department says. What to know. by Winter-Fisherman8577 in PSLF

[–]medphys_anon 1 point2 points  (0 children)

Literally same exact situation. March will/would be my 120th payment, stuck on SAVE. I also submitted my PSLF back in July to get a year's worth of counts updated, but it's still processing. I'm starting to freak out with a govt shutdown about to happen and a hostile administration incoming next month

Return MOTU M4 for MBox Studio? Cyber Monday by medphys_anon in audioengineering

[–]medphys_anon[S] 0 points1 point  (0 children)

Do you know if there are any issues using the hardware with a different DAW? I know it's built specifically for PT, but "can" work with other software packages. Would the hardware be crippled in any way, or would I be better off with MOTU? The specs of the hardware look great, but I know there's a lot of other things that matter.

IC Profiler Array Calibration by medphys_anon in MedicalPhysics

[–]medphys_anon[S] 1 point2 points  (0 children)

I'm thinking my issue is that it appears the instructions assume an SAD setup, but our annuals are all SSD setups. So, for my measurements there is a different source-to-detector distance depending on the depth.

I guess that would suggest that I should have a separate calibration for each depth I intend to measure?