jacione / ptychodactyl

A simple, approachable ptychography experimental pipeline written in Python.

Summary

• 👋 Hi, I'm Nick Porter (@jacione).
• 👨‍🎓 I'm currently working toward a PhD in physics at Brigham Young University.
• 👀 I’m interested in coherent diffraction imaging, algorithm development, device interfacing, experimental automation.
• ⌨ I'm pretty good with Python, with a vague grasp of C, C++, Javascript, and a few other languages.
• 🌱 I’m currently learning about GPU-accelerated computing.
• 💞️ I’m open to collaborate on pretty much anything.

Fun facts about me

• I've never broken a bone, but I have knocked out a few teeth.
• I made an RC car from scratch for my 2-year old. It took me the better part of a summer to design and build it. It took him the better part of 15 minutes to break it. I'd do it again in a heartbeat.
• I made a techno album when I was 21. It's... ok.

ptychodactyl's Issues

Automatic Reconstruction Runs

So, what I'm thinking is looking at being able to run the code so that you can input a certain number of different iterations to run so that the code itself can run through the iterations and save images of the data without having to be set to the new data set by human hand whenever it ends.

One example of this is you could set up a code perhaps where you have multiple strings where each string contains the parameters you want to run for one reconstruction, ie no flip images, at an angle of 11.25 and for 40 iterations of epie. Then, once this finishes, the code would save the output tables to a data file and move on to collect the next string of inputs and once again run the code according to the input given.

This way, we would be able to run multiple reconstructions at a time and greatly consolidate how much time it takes to run reconstructions on the data, as this could be run overnight, instead of just having one iteration run overnight.

It could also be that the data plots don't need to be saved as all, but rather could just be left open as they normally are, and then when we go to collect the data the next day, we have them open in the same order as they were inputed, as we have the input data page where we defined each iteration of reconstruct.py

Save reconstruction configuration in the pty file