carolinejia22
commented
2 years ago Matlab looks more sustainable and applicable to other applications in lab. The function you proposed looks like it only does images? Are you planning on extracting all images and cropping and then merging them back together?
Caroline
On Mon, Jan 31, 2022 at 11:06 PM Jeremy Delahanty @.***> wrote:
@rpamintu https://github.com/rpamintu and @hadiviko https://github.com/hadiviko have expressed interest in making a way forward for cropping videos in a flexible way for use in AlphaTracker pipelines. There's currently a Jupyter Notebook that's been written by a former lab member, Shristi, for @carolinejia22 https://github.com/carolinejia22 and uses moviepy for performing the cropping.
Unfortunately, there were inconsistencies in how recordings were performed (which will be corrected in the future). Thus, many of the recordings have inconsistent locations inside the video frame for home cage sociability recordings. We need a way of cropping this sort of data in a reproducible, easy to use, and documented manner.
What can come of this project is creating a general purpose image cropping tool that can output correctly formatted single images or videos that the lab can use.
There are two options I see for moving forward here:
- MATLAB: MATLAB has an image cropping tool that can perform this task for us it seems. See this link https://www.mathworks.com/help/images/ref/imcrop.html. We can probably make something much quicker than we could in Python if we use this. The primary issue is that we would either need to get you all MATLAB installed on your laptops (expensive, no thanks) or you can hop onto the cluster to use MATLAB licenses there. This option is ideal, plus you can get familiar with using the cluster generally. It's not too scary, I promise!
- Python: Python's OpenCV library has many ways of performing this sort of cropping by letting you make apps that can draw over images, perform a crop for all images in a video, and then write it all to some kind of output. This will require much more work than the MATLAB option most likely and, therefore, might not be the preferred method of moving forward with this. However, on the other hand, it would offer the best opportunity to learn a lot more about image manipulation details than the solution MATLAB offers you.
Comment on this post (it's fun!) for what you think. Try reacting to the post too for voting: ❤️ for python, 🎉 for MATLAB.
Regardless of the option you choose, the following will need to be done:
REQUIRED
- Where will this data be stored on the server? We need to have all videos have a consistent naming convention (ideally one that other teams in the lab could also use) and stored in a way that's structured, easy to programmatically write to and read from.
- What should the outputs look like? Where will those go?
- How should we keep track of the different things that have been completed for each step? This is something I've been grappling with and have probably been trying to make far too complicated. A simple spreadsheet for now would work fine, but ideally it could be checked by a script that anyone in the lab could quickly run to see what's been through what step without having to check directories themselves.
OPTIONAL BUT COOL
- How do we make this a reliable, easy thing to use for anyone in the lab for any purpose?
- Can we make a template for different use cases that can run different things in batches?
If you choose to do the Python version, there's a few other things we could do that would be great for you to learn about if you plan on doing any sort of larger than memory data processing (which if you do any sort of functional imaging like 2p/1p or even large ephys recordings, you will do one day! It's the future happening now!).
- Use Zarr as a data storage format for video data (I can explain Zarrs later if you're interested)
Let me know what you think. Depending on how you vote we'll move from there...
— Reply to this email directly, view it on GitHub https://github.com/Tyelab/specialk/issues/3, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVIV4TFU2F7C66F4U63SHGTUY6BBFANCNFSM5NIKGELA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>
jmdelahanty
@rpamintu and @hadiviko have expressed interest in making a way forward for cropping videos in a flexible way for use in AlphaTracker pipelines. There's currently a Jupyter Notebook that's been written by a former lab member, Shristi, for @carolinejia22 and uses
moviepyfor performing the cropping.Unfortunately, there were inconsistencies in how recordings were performed (which will be corrected in the future). Thus, many of the recordings have inconsistent locations inside the video frame for home cage sociability recordings. We need a way of cropping this sort of data in a reproducible, easy to use, and documented manner.
What can come of this project is creating a general purpose image cropping tool that can output correctly formatted single images or videos that the lab can use.
There are two options I see for moving forward here:
Comment on this post (it's fun!) for what you think. Try reacting to the post too for voting: :heart: for python, :tada: for MATLAB.
Regardless of the option you choose, the following will need to be done:
REQUIRED
OPTIONAL BUT COOL
If you choose to do the Python version, there's a few other things we could do that would be great for you to learn about if you plan on doing any sort of larger than memory data processing (which if you do any sort of functional imaging like 2p/1p or even large ephys recordings, you will do one day! It's the future happening now!).
Let me know what you think. Depending on how you vote we'll move from there...