Support EQDSK field#318
Conversation
|
@Sichao25 can you take a look at what the configuration issue is? I got a bit behind on approving PRs while asics was offline. |
|
@jacobmerson We have two pending updates in self hosted tests #322 and cmake tests #321 . |
|
Thanks I had missed those. They are merged now. |
|
I think we should add |
|
@jacobmerson The new constructor has been implemented. |
| * @return EQDSKFieldWithData A struct containing the data, function space, | ||
| * and populated field, ready for evaluation. | ||
| */ | ||
| inline EQDSKFieldWithData MakeEQDSKField(const std::string& filename) |
There was a problem hiding this comment.
@usmanriaz07 Are there potentially other fields in the EQDSK that may need to be evaluated later, or is the only field we evaluated in the eqdsk the psi field?
There was a problem hiding this comment.
We do use poloidal current value in the field line tracing. See the following piece of code:
https://github.com/SCOREC/STOMMS/blob/main/stomms_meshgen/src/eqdskData.cc#L197-L203
In ezfit.F90, the relevant function is: https://github.com/SCOREC/STOMMS/blob/main/stomms_meshgen/src/ezfit.F90#L562-L578
Other than poloidal current, we only need psi field.
| namespace pcms | ||
| { | ||
|
|
||
| struct EQDSKField |
There was a problem hiding this comment.
Is there ever a time where we would have an eqdsk with no data associated with it?
There was a problem hiding this comment.
There will always be an EQDSKData, but it doesn't have to be created with the helper functions defined here. It can be constructed manually instead of loaded directly from a file. The struct defined here is just for return values.
Support the load of EQDSK file and perform evaluation with uniform grid spline interpolator. Followed the data structure implemented in STOMMS. Close issue #242