-
Notifications
You must be signed in to change notification settings - Fork 4
Support reading surface data from an HDF5 file #92
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
Author
|
Here is a verification case. Here is part of the results for Here is part of the results for |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now users can use an HDF5 file providing surface data.
case_surface = 5&input_surf = "test.h5". (The option to read Boozer surface is nowcase_surface=3.)Nfp: int, number of toroidal periodicityIsSymmetric: int, stellarator symmetry option (0: no syemmtry; 1: toroidally periodic; 2: periodic and stellarator symmetric)disfac: double precision, the discretization factor for surface integration, usually is2*pi/Ntheta * 2*pi/Nzetaxsurf: double precision (Ntheta*Nzeta), x coordinates of the surface elementsysurf: double precision (Ntheta*Nzeta), y coordinates of the surface elementszsurf: double precision (Ntheta*Nzeta), z coordinates of the surface elementsnx: double precision (Ntheta*Nzeta), x coordinates of the surface unit normalny: double precision (Ntheta*Nzeta), y coordinates of the surface unit normalnz: double precision (Ntheta*Nzeta), z coordinates of the surface unit normalnn: double precision (Ntheta*Nzeta), the surface jacobian (normal vector magnitude)plas_Bn: double precision (Ntheta*Nzeta), target Bn (FOCUS usesBn_coil - Bn_targetThere are also some limitations.
dr/dthetaanddr/dzetacomponents are not read. Sotorfluxis not computed correctly. One can fix or constrain coil currents, instead.surfcoodis called. It reads(theta, zeta)and returns(R, Z). When reading the HDF files, Fourier coefficients for the surface are unknown. Sosurfcoordnow returns the nearest point in the given surface data. In short, initial circular coils and initial magnetic axis will be slightly different.