-
Notifications
You must be signed in to change notification settings - Fork 0
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
Specifying reference values in TGLF/CGYRO input files #326
Comments
Good question. FYI, Emily and I generally encourage users to not run with |
Yeah I think that would be fine. Something like a |
OK, I'm fine to move forward with this. |
For my two cents, I think it would be great to add to the out.cgyro.units, but would really like to keep the information in out.gyro.info<http://out.gyro.info> as well. I find a lot of utility in running of input.gacode directly, and think that workflow has some advantages for avoiding mistakes when dealing with many different experiments or sets of profiles. Happy to discuss further next week when back from IAEA.
…-Chris
----------------------------------------------------
Christopher Holland
Research Scientist
Center for Energy Research
UC San Diego
460 Engineering Building Unit II
School of Engineering, UCSD
9500 Gilman Drive, Mail Code 0417
La Jolla CA 92093-0417
Pronouns: he/him/his
Webpage: http://cer.ucsd.edu/_profile-pages/holland.html
on site at General Atomics
GA Office: 13-316
GA Phone: (858)455-4017
GA Fax: (858)455-3586
----------------------------------------------------
On Oct 18, 2023, at 5:34 PM, Jeff Candy ***@***.******@***.***>> wrote:
OK, I'm fine to move forward with this.
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https://github.com/gafusion/gacode/issues/326*issuecomment-1768926256__;Iw!!Mih3wA!HSbW4vaSEqfHH8fl80PPTaWqGkinXs17rRIXUwMr11b63ykjpYkEHr3dftVxi9h4mMkRflDWIhORzZEcyEVJhV7iJw$>, or unsubscribe<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AAE5BT4BBQM473A4TI7MPPTYAAAJFAVCNFSM6AAAAAA6FFX5M2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRYHEZDMMRVGY__;!!Mih3wA!HSbW4vaSEqfHH8fl80PPTaWqGkinXs17rRIXUwMr11b63ykjpYkEHr3dftVxi9h4mMkRflDWIhORzZEcyEWUqqDXUg$>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Would it be possible to add in the ability to optionally store the normalising reference values in standalone CGYRO/TGLF input files to allow for easier conversion to SI units. That or maybe a supplementary file which specifies these.
Ideally we'd want to store
$n_{e}$ , $T_{e}$ , $B_{unit}$ , $a$ and optionally $m_{ref}$
When running with an input.gacode file these are specified in the
out.cgyro.info
file so there is some capability already.The text was updated successfully, but these errors were encountered: