-
Notifications
You must be signed in to change notification settings - Fork 106
Add <1/R> to geometry and calulate spr from <1/R> #1413
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
Conversation
|
@felicif , @theo-brown is carrying out the an extension of the geometry inputs to include the 1/ term. Where can this be found in the LY structure? EDIT: nvm, it's Q0Q |
33cef24 to
0a816d5
Compare
Effect of changes on test casesTLDR: Minor differences in j profiles (and hence Ibs), De, Ve, Qalpha (and hence P alpha). Differences can be pronounced in chi, but only for one or two timesteps before returning to better agreement. These differences tend to not make a difference to overall behaviour of the simulation. Sawteeth behaviour has been altered, but I need a second pair of eyes to ascertain whether it's ok. iterhybrid_predictor_corrector casesObserve differences in chi, D_e, j, Qalpha, but without any real impact on the wider behaviour. iterhybrid_rampup casesObserve how De is very different for one timestep but then returns to agreement for the next timestep. test_iterhybrid_rampup_sawtoothMore pronounced flattening effect in the core. @jcitrin is this within the margin of acceptable changes to tests? |
|
ec1988b to
157eaf1
Compare
Regarding the sawteeth, it's probably just because the sawtooth crash times are now slightly different, and in that specific time slice you see one simulation post-crash and the other is more recovered. Here what matters more is the average over time rather than the difference at one time slice. e.g. if you plot Te[0] of simulations over time, as well as the average difference over multiple sawtooth crashes. If the compare_sim_test scripts are showing small differences for the averaging, then it should be fine. |
Likely related to stiffness and very slight profile differences triggering for one time slice a seemingly large difference. Over time the averages should be quite similar |
We have an internal notebook to regenerate those, which I think should be exposed if you need it. However, the quickest would be to just leave it for now and we will regenerate those refs during internal review. In due course we'll make the regeneration script public and provide instructions on its use |
Strange that it's failing. By how much? However look again I think that comparing the mean is a bit weird. We should be comparing all elements the cumulative integral (using spr as the metric coefficient), i.e. the plasma current up to a given flux surface. That should hold since the only components of plasma current in the test case is Ohmic and bootstrap. Feel free to change it, otherwise can leave it and we'll look at it during internal review |
Q0Q should always be present |
torax/torax/_src/core_profiles/tests/initialization_test.py Lines 170 to 172 in 4b3c09c
To keep this PR well-scoped I might just boost the tolerance, and leave a note. |
Remaining failing CI is only the tests from this file. |
44412c9 to
30c0d66
Compare
|
Looks great! Happy to bring it in after the one requested change. |
d2f4814 to
dd8b6bb
Compare
|
Thanks for the review @jcitrin. Made the change and updated the necessary test files (changes were order 1e-4). Reminder that the remaining tests failing are due to |
Change-Id: I1091f942084e127bc59e1677a87e61a0d7003ff1
Change-Id: Idf6c11c8fb445ad38d2cd1068dd8c28a1569c2fc
PiperOrigin-RevId: 796935939
Change-Id: I80eae659e8d85ba1a71550721b427531929f5105






Uh oh!
There was an error while loading. Please reload this page.