-
Notifications
You must be signed in to change notification settings - Fork 902
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Tutorial: Detection of Mitoflashes #5514
base: main
Are you sure you want to change the base?
Conversation
* detection-of-mitoflashes al branch detection-mitoflashes-tutorial * Update tutorial.md
updated tutorial data and tutorial data link
added another citation
Added License and output labels
Hi @kostrykin! When you have time, could you please check the tutorial again? I submitted it for review. I wanted to add an image that shows/explains the biological mechanism of mitoflashes but couldn't find one with a flexible license. If you have ideas on an image or can add an image to the tutorial, I think it will super helpful. |
…pturing-mitoflashes-tests.yml Co-authored-by: Leonid Kostrykin <void@evoid.de>
Co-authored-by: Leonid Kostrykin <void@evoid.de>
Co-authored-by: Leonid Kostrykin <void@evoid.de>
Co-authored-by: Leonid Kostrykin <void@evoid.de>
Co-authored-by: Leonid Kostrykin <void@evoid.de>
Co-authored-by: Leonid Kostrykin <void@evoid.de>
Co-authored-by: Leonid Kostrykin <void@evoid.de>
Added Citations
…toflash Events.tabular
Co-authored-by: Leonid Kostrykin <void@evoid.de>
Co-authored-by: Leonid Kostrykin <void@evoid.de>
...als/detection-of-mitoflashes/workflows/test-data/Spot Detection for Mitoflash Events.tabular
Outdated
Show resolved
Hide resolved
Uploaded test data files to Zenodo and added the links to the path of the test files.
…st (#2) Co-authored-by: dianichj <DCJPython@users.noreply.github.com>
Thanks a lot @kostrykin. I checked the file where I missed the Oxford comma. I hope that I didn't miss any comma spots. I also added two images to the tutorial. One of the them is of the Curve fitting file output. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Much thanks for all your work @dianichj
I have a few more comments :)
> - **Penalty**: Choose *Least absolute deviations (LAD)* for robust fitting to intensity fluctuations. | ||
> - **Alpha**: Set a significance level, such as `0.01`, to generate assistive curves if needed. | ||
> | ||
> This step applies polynomial curve fitting to model intensity fluctuations over time, identifying mitoflash events when intensity values exceed the fitted curve by the given significance level. Key parameters to analyze are **Amplitude** (peak intensity), **Tpk** (time to peak), and **T50** (duration). These values provide initial insights into mitochondrial function, with further interpretation outlined in the following section. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not quite clear what the parameters Amplitude, T50, and Tpk refer to. The tool doesn't have those parameters?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for asking! These parameters—Amplitude, Tpk, and T50—are not input parameters of the tool but are derived metrics used to measure mitoflash events. In biology, they are commonly reported to quantify and analyze mitochondrial dynamics.
For example:
- Amplitude measures the peak intensity of the flash.
- Tpk reflects the time it takes to reach this peak.
- T50 indicates the duration of the flash.
These values are useful for plotting and interpreting mitoflash dynamics in biological studies. Perhaps it would be more accurate to call these "metrics that can be extracted from the output for plotting"?
Several papers mention these metrics; for example, this one.
Rather than being annotations, these metrics are quantitative descriptors that help summarize and interpret key features of mitoflash events. Please let me know what you think and if this helps the clarification. I wanted to add this info to guide the user to the analysis and interpretation part.
|
||
With our data results, we can analyze their frequency, duration, and intensity. This data helps us understand the physiological significance of mitoflashes in processes like muscle contraction, neuron development, and wound healing. | ||
|
||
![Curve fitting results mitoflash](../../images/detection-of-mitoflashes/Curve_fitting_results_mitoflash.png "Mitoflash Curve Fitting Results: Data for plotting.") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very cool! Now this might be somewhat picky of me, but if you have the time, I think it would be better to show the table for a different spot (I suspect that there is a spot for which the INTENSITY value somewhere exceeds the CURVE_A value, is there?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will find it and add it =D! Maybe we can add a question here for it then? - Hahah more work
4. **CURVE** and **CURVE_A**: Contain fitted curve data that smooths out noise to highlight true intensity peaks. **CURVE** is the main fit, while **CURVE_A** may show adjusted fits if available. | ||
|
||
- **Amplitude (F/F0)**: The peak value in **CURVE** or **CURVE_A**, representing the magnitude of each mitoflash. Higher amplitudes indicate stronger bursts, which can have biological significance. | ||
- **Tpk (Time to Peak)**: The frame where **CURVE** or **CURVE_A** reaches maximum intensity, indicating the speed of each mitoflash. | ||
- **T50 (Duration)**: The frames where the curve values are at least half of the peak value, representing the mitoflash duration. Longer durations may reflect sustained mitochondrial activity. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Co-authored-by: Leonid Kostrykin <void@evoid.de>
Co-authored-by: Leonid Kostrykin <void@evoid.de>
Co-authored-by: Leonid Kostrykin <void@evoid.de>
Co-authored-by: Leonid Kostrykin <void@evoid.de>
New Imaging Tutorial Alert! 🚨🔬🚀
Summary:
This PR introduces a new tutorial for the Detection of Mitoflashes workflow. It guides users through tracking mitochondrial movement and identifying mitoflashes using Galaxy tools, covering data preparation, mitochondrial region detection, movement tracking, and mitoflash analysis.
TODO:
tutorial.md
follows the required structure and format for Galaxy tutorials.cc: @kostrykin 🤝