Open lazersos opened 3 months ago
A little background as to why I @lazersos didn't finish this part when I had a chance. TLDR: the IDS for coils are a mess. There are three IDS coil types in IMAS
Now my thought was to the the interface working such that if the user could call the code with a mix of coil IDS. The general flow would be:
LIBSTELL
to generate a B-field on a grid in MGRID.mgrid_mod
, VMEC should just behave like it read an MGRID.NOTE: some of my nomenclature here may be off.
VMEC has been interfaced as a fixed boundary solver in IMAS via iWrap. The basic idea is that iWrap wrappers fortran code VMEC provides, allowing the passing of IDS's back and forth. All the iWrap stuff can be found in the
IMAS_INTERFACE
directory and the VMEC interface code can all be found inVMEC2000/Sources/TimeStep/vmec_imas.f90
. This issue is to help track the implementation of free boundary VMEC into IMAS.