Skip to content
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

Open
wants to merge 47 commits into
base: main
Choose a base branch
from

Conversation

dianichj
Copy link
Contributor

@dianichj dianichj commented Nov 7, 2024

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:

  • Polish the tutorial content for clarity and quality.
  • Verify that all tool links in the tutorial are correct and functional. Update links if necessary.
  • Review all new files to ensure they are in the correct format and contain accurate content:
    • Confirm that tutorial.md follows the required structure and format for Galaxy tutorials.
    • Check any included datasets, images, and supplementary files for accuracy and relevance.
    • Ensure that all files meet Galaxy Training Network (GTN) standards.
  • Confirm that any images used are approved for re-hosting by the GTN and are appropriately licensed.
  • Test each step in the tutorial workflow to ensure completeness and accuracy, making modifications as needed to improve clarity and usability.

cc: @kostrykin 🤝

* detection-of-mitoflashes al branch detection-mitoflashes-tutorial

* Update tutorial.md
@dianichj dianichj marked this pull request as ready for review November 12, 2024 13:40
@dianichj
Copy link
Contributor Author

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.
Thank you!

dianichj and others added 13 commits November 13, 2024 10:03
…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
Co-authored-by: Leonid Kostrykin <void@evoid.de>
Co-authored-by: Leonid Kostrykin <void@evoid.de>
dianichj and others added 3 commits November 14, 2024 14:44
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>
@dianichj
Copy link
Contributor Author

dianichj commented Nov 14, 2024

Fantastic job, @dianichj!

A few comments inside.

Please also consider using the Oxford comma. I'm not aware of any guideline by the GTN, but personally I think it greatly improves readability in technical documents.

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.

Copy link
Contributor

@kostrykin kostrykin left a 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.
Copy link
Contributor

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?

Copy link
Contributor Author

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.")
Copy link
Contributor

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?)

Copy link
Contributor Author

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

Comment on lines +156 to +160
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.
Copy link
Contributor

@kostrykin kostrykin Nov 15, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this needs to be adapted to be more consistent with the description of the curves above (see this and this comment). Where do those terms Amplitude, Tpk, T50 come from? I couldn't find them in the curve fitting tool.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants