Title: docs: add physics callout box for Higgs search data distribution #127

[Riya-code2003]

This PR addresses issue #127 by adding a challenge/callout box to the Higgs search module (Episode 4).
​As an MSc Physics student, I have added a "Physics Tip" to clarify the distinction between experimental Data (ATLAS points) and Monte Carlo (MC) simulations in the invariant mass plot. This helps students understand the significance of the 125 \text{ GeV} Higgs signal peak.
​Changes
​Inserted {: .challenge} block before the Data vs. MC exercise.
​Used LaTeX formatting for units and particle decay notation.

[michmx]

Thanks @Riya-code2003 ! To clarify, this is not addressing #127 , as the issue is intended to explain the Python unpacking

fig, (ax_1, ax_2) = plt.subplots(1, 2)

However, it is a welcoming contrubition. It is true that for newcomes the logic of data/MC plots may not be evident.

So my suggestion is to address in the same PR the python unpacking fig, (ax_1, ax_2) = plt.subplots(1, 2). In other words, explain what that line of code is doing.

I am also adding @amorenobr and @ariostas in case they have other comments

[Riya-code2003]

Thanks @Riya-code2003 ! To clarify, this is not addressing #127 , as the issue is intended to explain the Python unpacking

fig, (ax_1, ax_2) = plt.subplots(1, 2)

However, it is a welcoming contrubition. It is true that for newcomes the logic of data/MC plots may not be evident.

So my suggestion is to address in the same PR the python unpacking fig, (ax_1, ax_2) = plt.subplots(1, 2). In other words, explain what that line of code is doing.

I am also adding @amorenobr and @ariostas in case they have other comments

Thanks @Riya-code2003 ! To clarify, this is not addressing #127 , as the issue is intended to explain the Python unpacking

fig, (ax_1, ax_2) = plt.subplots(1, 2)

However, it is a welcoming contrubition. It is true that for newcomes the logic of data/MC plots may not be evident.

So my suggestion is to address in the same PR the python unpacking fig, (ax_1, ax_2) = plt.subplots(1, 2). In other words, explain what that line of code is doing.

I am also adding @amorenobr and @ariostas in case they have other comments

Hi @michmx, thank you for the warm welcome and for clarifying the original intent of #127! I have updated the PR to include a section on Python tuple unpacking to explain the fig (ax_1, ax_2) syntax.

I also maintained the Physics Tip about the Higgs signal at 125Gev and Data vs. MC logic, as we agreed it's helpful for newcomers. I'm excited to contribute more to HSF training materials. Ready for another review whenever you have time!

[Riya-code2003]

Thanks for the review, @ariostas! I have addressed your comments by:

• Moving the challenge block line to 412 (closer to the relevant code)
• Updating the Markdown formatting to use backticks for code snippets.
• Adding the requested example for nested tuple unpacking.
  Let me know if there's anything else

[ariostas]

Let's keep the empty line here to separate things.

[Riya-code2003]

Done, I have restored the empty line after the image link to maintain proper spacing.

[ariostas]

It's still not empty. There's a >

[ariostas]

It's still not empty. There's a >

[ariostas]

Let's also remove the > here. And let's just leave one empty line.

[ariostas]

I think the comma should stay

[stale]

This issue or pull request has been automatically marked as stale because it has not had recent activity. Please manually close it, if it is no longer relevant, or ask for help or support to help getting it unstuck. Let me bring this to the attention of @amorenobr @vlukashenko @richa2710 @michmx for now.