- updated C2F copy routines to allow for skipping the pointers (in case of module initially defining the pointers in Fortran code in instead of C/C++ code)
- updated pack/unpack routines to avoid putting entire arrays on the stack (OpenFAST#99)
- updated extrap/interp routines to account for values that have a period of 2pi. This change requires additional routines in NWTC_Num.f90.
- this also includes changes that were introduces in a not-yet-merged pull request for 2D airfoil interpolation

- Use less stack space in interpolation/extrapolation, pack, and unpack routines (fixes OpenFAST#99).
- update auto-generated types files
- update interp/extrap routines work on angles (over 2pi boundaries); this requires Angles_ExtrapInterp routines added to NWTC Library
- NWTC Library
  + when reading real variables from file, check that they aren't Inf or NaN
  + remove unused code
  + add error handling to VTK read routines
  + check that size of scalars matches between meshes in transfer of data
  + add an (optional) reference node to mesh data structures

- continuous states are R8Ki (for VTK mode shapes)
- Use ChanLen instead of hard-coded sizes

- use 2pi interpolation on a few inputs/outputs
- add some init outputs for linear trim solution
- modify input/output mesh packing routines for VTK visualization

- added nodal outputs ([optional] change in input file) -- CHECK value of ChanLen
- placeholder for NeedWriteOutput
- updated routine to compute AD_JacobianPInput (will not give error about being non-differentiable)

- nodal outputs (check length of channel name)
- send optional flag to avoid calculating WriteOutputs if they won't be used in this step
- minor changes to use log maps in mesh packing for linearization

- remove prev outputs from SrvD inputs (for DLL); store them in misc vars instead
- move call to controller to UpdateStates instead of CalcOutput
- rework some of the DLL capabilities (move data structures around) 
  + HSSBrake can now use avrSWAP107 (or SrvD will implement a linear ramp--change comment in input files about this); 
- trim case logic for linearization

also sync some other subroutines + types file

The units on the YawMomCom write-output channel in the linearization matrices were wrong. This would only be noticeable if you requested the YawMomCom channel from ServoDyn along with linearization matrices that included the outputs.

Adds
- trim solution
- vtk mode-shape visualization
- vtk file-name stored as parameter instead of recalculating each time
- ED%Output(1) renamed to ED%y for consistency (Output now used in save OP for trim solution)
- additional damping may or may not actually work
- CHECK: length of channel names (file format?)
- simulink interface now allows 4000 channels instead of 1000 (all blade node outputs can significantly increase number of channels generated)
- added logic to avoid calculating WriteOutput array when it is not necessary

Someone should document these, too.

This is not used in OpenFAST, yet.

- Added `WP_Baseline` to list of directories to copy
- Replaced `is` and `is not` with `==` and `!=` when comparing with a string literal (else they would always return false)

This should be unnecessary after changing the length of the rest of the output channels. **However, it may cause some grief in the FAST.Farm code.**

- also modifies the binary output file

- also fix issues in new code found in debugging
- WE SHOULD CHECK THAT LINEARIZATION IS OFF when using FAST.Farm, Simulink, CFD interface, and any other cases where we are modeling more than one turbine

I was tired of seeing warnings about the deprecated "legend" keyword

also make nodal outputs for AD and BD allow 3 digits in the node number

Otherwise, they may overlap with structural nodes

Baseline and local were switched
also fix syntax of legend label

Update of VS solution

OpenFAST#382

Sorry, Jeff Minnema. I think your name has been spelled wrong in there for quite a while!

previously worked for only 1-dimensional arrays

Make sure HydroDyn inputs are set from ElastoDyn outputs in fixed-bottom simulations prior to starting the solve option 1 code. I don't expect this to have much effect on the results, but this more closely follows the implementation plan.

Also fixed some typos in comments

@jjonkman and @ghaymanNREL may want to incorporate this in other branches they are working on.

added some quotation marks in case of spaces in path names
added "call" to command line

- remove unused code
- update text formatting
- add version header file to vs-build
- fix some error handling in OpenFOAM.f90

fix merge conflicts from new NREL code yet again.

AD was not telling the glue code what time step it is requesting, so if the value "DTAero" in the AD input file was not "default" or the value of the glue-code time step, there could be inconsistencies in the results.

This is part of a reorg for the next Envision-NREL collaboration: replaced individual module initInput/InitOutput types in FAST_Subs.f90/FAST_InitializeAll() with a type defined in FAST_Registry.txt.

Note that I removed ability to linearize with ExtPtfm model in OpenFAST because it isn't fully implemented (i.e., the input-output solves aren't in the linearization matrices). I also commented out the ExtPtfm standard inputs because it seems like they should be just normal inputs. At the minimum, these should be documented before being included here.

That one's been in there for a LONG time

F/linear updates

This prevented the SS_Excitation from working

also fixed some comments

Also minor change on wording in AD error message

Reg test: Update the linearization output format

f/Linear -- documentation updates for nodal outputs