Skip to content

DOC: manual formulation of helicity amplitudes for pgamma->LambdaKPi - #104

Open
shenvitor wants to merge 13 commits into
mainfrom
manual-lambdakpi
Open

DOC: manual formulation of helicity amplitudes for pgamma->LambdaKPi#104
shenvitor wants to merge 13 commits into
mainfrom
manual-lambdakpi

Conversation

@shenvitor

@shenvitor shenvitor commented Sep 2, 2024

Copy link
Copy Markdown
Member

@shenvitor shenvitor self-assigned this Sep 2, 2024
@shenvitor
shenvitor requested a review from a team September 2, 2024 14:20
@shenvitor shenvitor added ✨ Feature New feature added to the package 📝 Docs Improvements or additions to documentation labels Sep 2, 2024
@shenvitor
shenvitor marked this pull request as draft September 6, 2024 15:14
@shenvitor
shenvitor marked this pull request as ready for review September 6, 2024 15:14

@redeboer redeboer left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Looks like going in the right direction 💪
See comments and be careful to rename the PR to a conventional commit message

Comment thread docs/lambda-k-pi/manual-dpd.ipynb Outdated
Comment thread docs/lambda-k-pi/manual-dpd.ipynb Outdated
Comment on lines +229 to +231
"zeta_1_0, zeta_1_1, zeta_2_0, zeta_2_1, zeta_3_0, zeta_3_1 = sp.symbols(\n",
" r\"\\zeta_{1(1)}^0 \\zeta_{1(1)}^1 \\zeta_{2(1)}^0 \\zeta_{2(1)}^1 \\zeta_{3(1)}^0 \\zeta_{3(1)}^1\"\n",
")\n",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

In this case I would use sp.Symbol and define each zeta separately. It's more scalable and helps finding bugs if each symbol definition is below the other.

Comment on lines +333 to +343
"A1 = (\n",
" formualte_A1(\"K^{*}(1410)^+\", 1)\n",
" + formualte_A1(\"K^{*}(1680)^+\", 1)\n",
" + formualte_A1(\"K^{*}(892)^+\", 1)\n",
" + formualte_A1(\"K^{*}_0(1430)^+\", 0)\n",
" + formualte_A1(\"K^{*}_0(700)\", 0)\n",
" + formualte_A1(\"K^{*}_2(1430)\", 2)\n",
" + formualte_A1(\"K^{*}_3(1780)\", 3)\n",
" + formualte_A1(\"K^{*}_4(2045)\", 4)\n",
")\n",
"A1"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This will need to be automated, i.e., some loop over the $K^*$ resonances found by QRules, and computation of the helicity. Actually, your formulate_A1() is more something like formulate_chain_amplitude_a1() and formulate_a1() creates the coherent sum of those chain amplitudes.

" r\"s_{31} m_{\\Sigma^*} \\Gamma_{\\Sigma^*} C_{\\Sigma^*}\"\n",
")\n",
"theta31, phi31, delta = sp.symbols(r\"theta_31 phi_31 \\delta_{\\lambda_\\Sigma^*1/2}\")\n",
"d_s = sp.Function(r\"d_{\\lambda_\\Sigma^*1/2}^{1/2}\")\n",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Replace with Wigner.d and use directly inline in the expression definition

"metadata": {},
"outputs": [],
"source": [
"A1 = (\n",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Be careful not to overwrite the previous A1 definition. This should be the A1_expr, or even something like a mapping of sp.Symbol to sp.Expr as dictionary. Something like:

amplitudes = {}
amplitudes[A1[-half, +half]] = formulate_A1(...) + ...

@shenvitor shenvitor changed the title Manual formulation of helicity amplitudes DOC: manual formulation of helicity amplitudes for pgamma->LambdaKPi Sep 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

📝 Docs Improvements or additions to documentation ✨ Feature New feature added to the package

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Manually formulate symbolic helicity amplitude for pγ → ΛKπ

2 participants