Standardize code patterns for reading input files

[gonuke]

Each of the main parastell functions can be called independently as a script. We should develop a standard way to read and parse the yaml.

[connoramoreno]

This may have been addressed in #55 but I'll suspend closing this until confirmation by @gonuke

[gonuke]

I don't think this is quite ready.

First, I notice that in the current code in oo_version we don't all refer to the same data using the same keywords.

Second - and maybe overkill - but we could move the read_yaml_config to the utils and pass in a list of keywords to get back and then not have to reimplement these same ~6 lines in each file.

[connoramoreno]

1. Perhaps I'm misunderstanding what you mean but I'm failing to see where they're different (at least where the same arguments are used)
2. I think that's a good idea! We can just pass all_data back from read_yaml_config and have the corresponding script parse that data object

[gonuke]

I t

1. Perhaps I'm misunderstanding what you mean but I'm failing to see where they're different (at least where the same arguments are used)

I think I use vmec_file in source_mesh and you use just vmec in inboard_vessel? One of them is wrong?

[connoramoreno]

Both use vmec, which refers to the VMEC object created by PyStell-UW. vmec_file is only an input argument for parastell, which refers to the actual VMEC data file that is subsequently read into PyStell-UW and passed to invessel_build and source_mesh.

[gonuke]

I just updated invessel_build in #64 I think

[connoramoreno]

I missed that vmec was what's being returned by read_yaml_config in invessel_build; that's my bad. Thanks for changing that.

[connoramoreno]

Closed via #70