Skip to content
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

Open
bpatel2107 opened this issue Oct 18, 2023 · 4 comments
Open

Specifying reference values in TGLF/CGYRO input files #326

bpatel2107 opened this issue Oct 18, 2023 · 4 comments

Comments

@bpatel2107
Copy link
Contributor

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.

@jcandy
Copy link
Member

jcandy commented Oct 18, 2023

Good question. FYI, Emily and I generally encourage users to not run with input.gacode but instead to generate a local input file using the -loc_rad option of profiles_gen. Also, for experimental modeling TGYRO is better suited for computing the local gyrobohm factors and target fluxes. The original motivation for a separate tool (profiles_gen) to manipulate profile data was to separate the GK calculation from the profile manipulation. I think generation of a supplementary file is the better option that might even allow us to remove the information from out.cgyro.info. How about generation of the supplementary file using profiles_gen -loc_rad ?

@bpatel2107
Copy link
Contributor Author

Yeah I think that would be fine. Something like a out.cgyro.units would work great for most purposes.

@jcandy
Copy link
Member

jcandy commented Oct 18, 2023

OK, I'm fine to move forward with this.

@cholland
Copy link
Member

cholland commented Oct 19, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants