Fix wisdem api

[gbarter]

The WISDEM API became out of sync with the changes in the recent ORBIT release, which was flagged by users. To do a better job catching this next time, I wonder if:

• Maybe this WISDEM API file is owned by the WISDEM repository. That would aid in us just using ORBIT as a library
• There was a schema that checked the config-dictionary and provided warnings for unused entries. What do you think?

[nRiccobo]

Thanks for putting this together. I think there is definitely room to ensure WISDEM and ORBIT interface nicely. Especially through code updates. This api file always slips my mind as new ORBIT changes come through.

I'm open to either way at this point. We're working on a few more cost/project parameter updates - so we might have to repeat these steps. But, I'll review this and get it into dev so users can continue their work.

[gbarter]

Thanks for putting this together. I think there is definitely room to ensure WISDEM and ORBIT interface nicely. Especially through code updates. This api file always slips my mind as new ORBIT changes come through.

I'm open to either way at this point. We're working on a few more cost/project parameter updates - so we might have to repeat these steps. But, I'll review this and get it into dev so users can continue their work.

Thank you, Nick! On the last point, all the more reason to have some sort of "echo" of which config parameters are understood versus not. That way old analysis scripts or code get feedback when parameter values are not being passed through.

[nRiccobo]

I adjusted some of the variable names to be consistent with ORBIT's latest project_parameters. In future releases, some of these parameters (a.k.a soft costs) will be calculated based on the project size and type, rather than user-defined. However, ORBIT is still backwards compatible (for the most part) and allows the user to define USD/kW values for these parameters. For simplicity, I went this route and defined the default values as $/kW based on a 600MW (50 x 12MW) plant.

[nRiccobo]

Thanks for bringing this up!

[gbarter]

I adjusted some of the variable names to be consistent with ORBIT's latest project_parameters. In future releases, some of these parameters (a.k.a soft costs) will be calculated based on the project size and type, rather than user-defined. However, ORBIT is still backwards compatible (for the most part) and allows the user to define USD/kW values for these parameters. For simplicity, I went this route and defined the default values as $/kW based on a 600MW (50 x 12MW) plant.

It would probably be easier for WISDEM to use the internal ORBIT calculation for many of these line entries, as that would better scale with design changes coming from WISDEM. Feel free to delete those parameters that have internal ORBIT calculations that are recommended best practice