update sam library files

[cwhanse]

pvlib python pull request guidelines

Thank you for your contribution to pvlib python!

You may submit a pull request with your code at any stage of completion, however, before the code can be merged the following items must be addressed:

• [X ] Closes issue update sam library files #440
• Fully tested. Added and/or modified tests to ensure correct behavior for all reasonable inputs. Tests must pass on the TravisCI and Appveyor testing services.
• Code quality and style is sufficient. Passes git diff upstream/master -u -- "*.py" | flake8 --diff and/or landscape.io linting service.
• New code is fully documented. Includes sphinx/numpydoc compliant docstrings and comments in the code where necessary.
• Updates entries to docs/sphinx/source/api.rst for API changes.
• Adds description and name entries in the appropriate docs/sphinx/source/whatsnew file for all changes.

Please don't hesitate to ask for help if you're unsure of how to accomplish any of the above. You may delete all of these instructions except for the list above.

Brief description of the problem and proposed solution (if not already fully described in the issue linked to above):

Updates sam library files for CEC module and CEC inverter models.

[wholmgren]

git annoyances strike again! My recommendation is to:

1. add a new "remote" so you can get the latest version on github. This associates the name "upstream" with the url, but does nothing more: git remote add upstream https://github.com/pvlib/pvlib-python.git
2. fetch the data from the upstream remote (this doesn't touch your data or any local changes you've made. it just stores it in a hidden directory): git fetch upstream
3. make a new local branch that's based on upstream/master: git checkout -b samupdate upstream/master
4. (re)apply your new commits. You can reapply commits manually or using git cherry-pick. You don't want to use git merge because that will pull the other unwanted changes in too.
5. push your new branch to github: git push --set-upstream origin samupdate
6. make a new pull request from the samupdate branch.

I use steps 2-6 for essentially every pull request.

Step 7 is repeat until it's muscle memory and doesn't feel like a hassle. The git flogging will continue until moral improves.

(The original comment contained commands that did not work, so I edited them)

[wholmgren]

closing this pull request in favor of #444