Hello! This for everyone to discuss (and share memes) about optical potentials and application of RBM emulators to them
For those that are interested in working on the project together, we are discussing emulating a simple coupled channels toy model with the RBM. The end result can be a Jupyter-notebook that adds a chapter to this book: Introduction to Reduced-Basis Methods in Nuclear Physics — Reduced Basis Methods in Nuclear Physics
I’ve made a branch off of the summer school github, that lives in my fork, that we can work off of, here: GitHub - beykyle/2023-FRIB-TA-Summer-School at omp-rbm
We should be able to work on this using code spaces as we have for all the exercises.
To add the omp-rbm fork as a remote on git:
git remote add omp-rbm-origin firstname.lastname@example.org:beykyle/2023-FRIB-TA-Summer-School.git
And then you can create a new branch and set the omp-rbm branch as the upstream like so:
git checkout -b <your-branch-name>
# make changes to the files, and add and commit them to your local branch
git push --set-upstream omp-rbm-origin omp-rbm
You will have to let me know if you want access so I can add you as a collaborator on github. Just send me the email associated with your github profile and I can add you.
We also have a WhatsApp, here is the link to join: WhatsApp Group Invite
I asked Kyle to talk about this application of the RBM for coupled channel scattering but I ended up not having enough time to sit down and chat. I would love to be involved in this project if there’s space for one more person.
I have thought a bit about how it could be implemented from my involvement with the ROSE project. Let me know if that’d work
Of course, we’d love to have you involved! All we’ve done so far is to start formulating the problem. We can set up a zoom this coming week to discuss the project.
Let’s do it! I will be at Caltech for most of this upcoming week. Monday is pretty free, the other days we can try to figure out a time in the morning.
Here is a when2meet survey for the rest of the week, if you’d like to chat, please fill it out: Coupled Channels RBM chat - When2meet
I’ll check it tomorrow and send the result and a zoom link.
@Edgard @aainabthapa @Dana-Abdallah @Simone
All we’ve done so far is discuss the problem, and we’ve drafted our problem statement here:2023-FRIB-TA-Summer-School/omp-rbm/coupled_channels_rbm.ipynb at omp-rbm · beykyle/2023-FRIB-TA-Summer-School · GitHub
This is of course open to changes, but we’d like to keep it simple given the week or so we have left.
I filled my availability. I’m at Caltech this week for work so my times are not very flexible. Hopefully there’s some overlap. If not I will try my best to be present for the scheduled time
Happy 4th of July to everyone, and very happy to have you aboard Edgard!
Thanks Kyle for rewriting and uploading the notes!
I attempted to create a pull request with a couple of small fixes,
When we stopped discussing last time we were considering two points:
- What parameters to vary. For a simple start, changing only the depths V, W, \beta, \gamma will simplify the evaluation of the couplings.
- What basis to use. We thought that it would be most convenient to use a separate basis for the ground state and each excited state, presumably just a set of solutions for those (for each set “a” of parameters, the \psi_0, \psi_1, \psi_2 in the notes). The alternative could have been to treat the tuple of solutions for each state as a single, longer vector, and make a basis for that.
It looks like Friday at 10am EDT is the best meeting time for everyone! Zoom info pasted at the bottom of the messageS
In the meantime, I’ll work on getting the high fidelity solver working for our problem, so we can focus on constructing the emulator.
Kyle Andrew Beyer is inviting you to a scheduled Zoom meeting. Topic: Coupled Channel RBM chat Time: Jul 7, 2023 10:00 AM Eastern Time (US and Canada) Join Zoom Meeting Launch Meeting - Zoom Meeting ID: 980 [2289 2822](tel:2289 2822) — One tap mobile +12532158782,98022892822#US (Tacoma) +13017158592,98022892822#US (Washington DC) — Dial by your location • [+1 253 215 8782](tel:+1 253 215 8782) US (Tacoma) • [+1 301 715 8592](tel:+1 301 715 8592) US (Washington DC) • [+1 305 224 1968](tel:+1 305 224 1968) US • [+1 309 205 3325](tel:+1 309 205 3325) US • [+1 312 626 6799](tel:+1 312 626 6799) US (Chicago) • [+1 346 248 7799](tel:+1 346 248 7799) US (Houston) • [+1 360 209 5623](tel:+1 360 209 5623) US • [+1 386 347 5053](tel:+1 386 347 5053) US • [+1 507 473 4847](tel:+1 507 473 4847) US • [+1 564 217 2000](tel:+1 564 217 2000) US • [+1 646 876 9923](tel:+1 646 876 9923) US (New York) • [+1 646 931 3860](tel:+1 646 931 3860) US • [+1 669 444 9171](tel:+1 669 444 9171) US • [+1 669 900 6833](tel:+1 669 900 6833) US (San Jose) • [+1 689 278 1000](tel:+1 689 278 1000) US • [+1 719 359 4580](tel:+1 719 359 4580) US • [+1 253 205 0468](tel:+1 253 205 0468) US • [+1 780 666 0144](tel:+1 780 666 0144)Canada • [+1 204 272 7920](tel:+1 204 272 7920)Canada • [+1 438 809 7799](tel:+1 438 809 7799)Canada • [+1 587 328 1099](tel:+1 587 328 1099)Canada • [+1 647 374 4685](tel:+1 647 374 4685)Canada • [+1 647 558 0588](tel:+1 647 558 0588)Canada • [+1 778 907 2071](tel:+1 778 907 2071)Canada Meeting ID: 980 [2289 2822](tel:2289 2822) Find your local number: Zoom International Dial-in Numbers - Zoom — Join by SIP • email@example.com — Join by H.323 • 184.108.40.206 (US West) • 220.127.116.11 (US East) • 18.104.22.168 (India Mumbai) • 22.214.171.124 (India Hyderabad) • 126.96.36.199 (Amsterdam Netherlands) • 188.8.131.52 (Germany) • 184.108.40.206 (Australia Sydney) • 220.127.116.11 (Australia Melbourne) • 18.104.22.168 (Singapore) • 22.214.171.124 (Brazil) • 126.96.36.199 (Mexico) • 188.8.131.52 (Canada Toronto) • 184.108.40.206 (Canada Vancouver) • 220.127.116.11 (Japan Tokyo) • 18.104.22.168 (Japan Osaka) Meeting ID: 980 [2289 2822](tel:2289 2822)
Agreed. If we stick with the affine dependencies (just depths) training and testing the emulator will be really easy.
I’m a bit more of a fan of using a single, longer vector. Because the equations we are modelling are inherently coupled and linear, so there will be more redundancy we can exploit. But I agree that a basis for everything is simpler, so maybe start there first.
I was reading the description on the github and got a bit confused. I had understood that the coupled-channel problem is just mixing states with different “l” numbers. If it is mixing different energies, what do we choose for “l” in each equation?
My understanding is that, if the potentials do not couple different angular momenta (as we want here, I guess), then you can solve for each single l separately, and they do not couple. In principle you have to solve for all l to get the full solution, but in practice one truncates somewhere reasonable for the energy of interest.
So coupled channels in general can be open to interpretation - it just means factorizing your Hilbert space into an elastic channels, as well as one or more discrete inelastic channels. Typically the elastic channel is the ground state of the target + the projectile, and the included inelastic channels are the excited states of the target + projectile.
The choice of model that describes those excited states is determined by what sort of phenomena need to be described. For example, for heavy nuclei, one might choose a collective model like the soft-rotor model, that describes rotational and vibrational excitations of the target. It is this choice of model that determines the coupling between angular momentum states. For example, for the soft-rotor model, each channel describes a given total angular momentum, and so the three contributing the angular momentum of 1) the target 2) the projectile and 3) the orbital angular momentum need to be coupled in such a way (e.g. through Racah coefficients) that adds up to the total angular momentum of the channel (and, for unpolarized beams/detectors, averages over total projection quantum numbers).
In our toy model, we’ve made up a simple thing that ignores angular momentum coupling entirely - e.g. our model Hilbert space is factorizable into a tensor product of energy and AM states. This is a very unrealistic simplifying assumption. In this case, it is as Simone describes; each orbital AM state is uncoupled to eachother, but the energy levels are coupled within each orbital AM state,
A better choice might be to assign the ground state and each excited state a fixed total angular momentum. Then (by Wigner-Eckhart theorem) the coupling between partial waves (orbital AM states) becomes purely geometric, and each excited state has contributions by a weighted sum of oributal AM states, with weights given by Racah coefficients (or, equivalently, Wigner-6j symbols). This increases the dimension of the Hilbert space dramatically, as each l state is now coupled, but is much closer to real problems so perhaps this is a better place to start.
Thanks for the more in-depth reply!
While it is indeed quite unrealistic, for our toy model, personally, I would go ahead imagining that we are coupling, say, three 0+ states, at least to start. Adding angular momentum coupling generates several technical annoyances but little physics insight.
I agree that this is probably the best place to start.
If we have time, we can extend to channels with non-zero total AM as I described. This would probably present the biggest technical challenge of how to construct the basis (e.g. one basis for each partial wave? each channel? tensor product somehow?) which would provide valuable insight into how best to do it with a realistic model (e.g. with a production code like Fresco as the high-fidelity solver). I think this can be really good “future work” for this project.
By the way, my long-term “dream” goals with this project would be to:
- construct an emulator for a rigid-rotor coupled channels optical model to calibrate to fission
- construct an emulator for this soft-rotor dispersive coupled channels optical model for actinides , as well as a new version with fully non-local potentials, calibrate them, and compare
Hey @aainabthapa , I’m finally getting around to reading this paper and I was wondering if there is a good source for numerical/computational details on the implementation of RPA/QRPA?