Fix vendor drop for 2.5.0

Accidentally dropped some files when I did the vendor drop.  Fix that.

.gitignore

@@ -0,0 +1,19 @@
+#
+# .gitignore for data-model
+#
+
+# Ignore python object code artifacts.
+*.pyc
+
+# Ignore some Mac-specific files.
+**/.DS_Store
+
+# ignore eclipse project files
+.project
+.cproject
+
+# ignore CLion and PyCharm project files
+.idea
+
+# ignore build dir
+build/

.gitlab/issue_templates/BugReport.md

@@ -0,0 +1,46 @@
+~"Bug Report"
+<!-- This template is based similar ones found in EMPIRE, written by Jason M. Gates -->
+
+## Description
+
+<!-- What went wrong? -->
+<!-- What should have happened? -->
+<!-- What might fix things? -->
+<!-- What's the impact of this bug? -->
+<!-- What is the goal of this bug fix? -->
+<!-- Is there a due date? -->
+<!-- Is this holding up an issue or milestone? -->
+
+
+## Steps to Reproduce? 
+
+| data-model   | OS  |Python Version | virtualenv? | C++ version | Boost version | package manager |
+| commit hash? |     |               |  yes/no     |             |               |                 |
+| branch       |     |               |             |             |               |                 |
+
+
+1. Netlist file? [attach here]
+1. Build Configuration? [attach here]
+1. Do this
+1. Do that
+1. Is their output from? [attach here]
+1. Is their a stack trace? [attach here]
+1. Is their an error message? [attach here]
+
+
+## Fixed Criteria?
+
+<!-- How can you demonstrate that this bug is fixed? -->
+
+
+## Weight/Importance
+
+| Question                                                                           | Points |
+|:---------------------------------------------------------------------------------- |:------:|
+| $`Q_1`$:  Is this time consuming to program or develop?  Yes = 5, No = 1           |        |
+| $`Q_2`$:  Is this difficult to test?  Yes = 3, No = 0                              |        |
+| $`Q_3`$:  Will the completion of this story rely on other people?  Yes = 3, No = 0 |        |
+| $`Q_4`$:  Is this work something you're familiar with?  Yes = 5, No = 1            |        |
+| **Total:**  $`(Q_1 + Q_2) \cdot (Q_3 + Q_4)`$                                      |        |
+
+/label ~"Bug Report"

.gitlab/issue_templates/Disussion.md

@@ -0,0 +1,32 @@
+~"Discussion"
+<!-- This template is based similar ones found in EMPIRE, written by Jason M. Gates -->
+
+## Description
+
+<!-- What do we need to discuss? -->
+<!-- Is there a specific decision we have to make? -->
+<!-- Is this a question you need an answer to? -->
+<!-- Why do we need to discuss it? -->
+<!-- @mention whoever should be part of this discussion -->
+
+
+## Completion Criteria
+
+<!-- How do we know when this discussion is complete? -->
+<!-- Is this part of another issue or milestone? -->
+
+* [  ] Talk about this
+* [  ] Figure out that
+* [  ] Discuss the next steps
+* [  ] Oh! One more thing ...
+
+
+## Weight/Importance
+| Question                                                                           | Points |
+|:---------------------------------------------------------------------------------- |:------:|
+| $`Q_1`$:  Is this time consuming to program or develop?  Yes = 5, No = 1           |        |
+| $`Q_2`$:  Is this difficult to test?  Yes = 3, No = 0                              |        |
+| $`Q_3`$:  Will the completion of this story rely on other people?  Yes = 3, No = 0 |        |
+| $`Q_4`$:  Is this work something you're familiar with?  Yes = 5, No = 1            |        |
+
+/label ~"Discussion"

.gitlab/issue_templates/Documentation.md

@@ -0,0 +1,30 @@
+~"Documentation"
+<!-- This template is based similar ones found in EMPIRE, written by Jason M. Gates -->
+
+## Description
+
+<!-- What do you want change in the documentation? -->
+<!-- Is this documentation in the code itself? -->
+<!-- It this for developers or users? -->
+<!-- It this a change to the user's guide? -->
+<!-- How has the lack of documentation impacted you? -->
+<!-- What's the goal of this work? -->
+
+
+## Done Criteria
+
+<!-- How can you demonstrate that this work is complete? -->
+<!-- Is there a due date? -->
+<!-- Is this associated with an other issue or milestone? -->
+
+
+## Weight/Importance
+
+| Question                                                                           | Points |
+|:---------------------------------------------------------------------------------- |:------:|
+| $`Q_1`$:  Is this time consuming to program or develop?  Yes = 5, No = 1           |        |
+| $`Q_2`$:  Is this difficult to test?  Yes = 3, No = 0                              |        |
+| $`Q_3`$:  Will the completion of this story rely on other people?  Yes = 3, No = 0 |        |
+| $`Q_4`$:  Is this work something you're familiar with?  Yes = 5, No = 1            |        |
+
+/label ~"Documentation"

.gitlab/issue_templates/FeatureRequest.md

@@ -0,0 +1,28 @@
+~"Feature Request"
+<!-- This template is based similar ones found in EMPIRE, written by Jason M. Gates -->
+
+## Description
+
+<!-- What feature or change is needed? -->
+<!-- How is this different from the current behavior? -->
+<!-- How might this be accomplished? -->
+<!-- What's the impact of not having this feature? -->
+<!-- What's the goal of adding this feature? -->
+
+
+## Completion Criteria
+
+<!-- How can we demonstrate that this work is complete? -->
+<!-- Is this work associated with an issue or milestone? -->
+
+
+## Weight/Importance
+| Question                                                                           | Points |
+|:---------------------------------------------------------------------------------- |:------:|
+| $`Q_1`$:  Is this time consuming to program or develop?  Yes = 5, No = 1           |        |
+| $`Q_2`$:  Is this difficult to test?  Yes = 3, No = 0                              |        |
+| $`Q_3`$:  Will the completion of this story rely on other people?  Yes = 3, No = 0 |        |
+| $`Q_4`$:  Is this work something you're familiar with?  Yes = 5, No = 1            |        |
+| **Total:**  $`(Q_1 + Q_2) \cdot (Q_3 + Q_4)`$                                      |        |
+
+/label ~"Feature Request"

.gitlab/issue_templates/Task.md

@@ -0,0 +1,32 @@
+~"Task"
+<!-- This template is based similar ones found in EMPIRE, written by Jason M. Gates -->
+
+## What needs to be done?
+
+What needs to happen and why?
+How does this relate to the rest of XDM or Xyce?
+List out the steps
+
+* [  ] First do this.
+* [  ] Then do that.
+* [  ] Oh, and this too
+
+
+## Completion Criteria
+
+<!-- What must we demonstrate to call this work complete? -->
+<!-- Is there a due date? -->
+<!-- Is this associated with another issue or Milestone? -->
+
+
+## Weight/Importance
+
+| Question                                                                           | Points |
+|:---------------------------------------------------------------------------------- |:------:|
+| $`Q_1`$:  Is this time consuming to program or develop?  Yes = 5, No = 1           |        |
+| $`Q_2`$:  Is this difficult to test?  Yes = 3, No = 0                              |        |
+| $`Q_3`$:  Will the completion of this story rely on other people?  Yes = 3, No = 0 |        |
+| $`Q_4`$:  Is this work something you're familiar with?  Yes = 5, No = 1            |        |
+| **Total:**  $`(Q_1 + Q_2) \cdot (Q_3 + Q_4)`$                                      |        |
+
+/label ~"Task"

.gitlab/merge_request_templates/BugReport.md

@@ -0,0 +1,29 @@
+~"Bug Report"
+<!-- This template is based similar ones found in EMPIRE, written by Jason M. Gates -->
+
+## Closes
+
+<!-- Which issue does this close? -->
+<!-- If there is no issue yet, create one then submit the merge request -->
+<!-- NOTE: the issue should have all info related to how the work done in this request impacts the other issues and milestones in the project. -->
+
+
+## Is there a test for this?
+
+* [  ] Modifies existing data-model unit test.
+* [  ] Creates new data-model unit test.
+* [  ] Modifies Xyce_Regression test.
+* [  ] Creates Xyce_Regression test.
+
+
+## Checklist
+
+* [  ] The python code is generally pep-8 compliant.
+* [  ] These changes are documented in the code.
+* [  ] These changes are documented in the developer guide/wiki.
+* [  ] These changes are documented in the user guide.
+* [  ] All new and existing test have passed.
+* [  ] No new C++ or Python warnings have been introduced.
+* [  ] These changes break backward compatibility.
+
+/label ~"Bug Report"

.gitlab/merge_request_templates/Documentation.md

@@ -0,0 +1,29 @@
+~"Documentation"
+<!-- This template is based similar ones found in EMPIRE, written by Jason M. Gates -->
+
+## Closes
+
+<!-- Which issue does this close? -->
+<!-- If there is no issue yet, create one then submit the merge request -->
+<!-- NOTE: the issue should have all info related to how the work done in this request impacts the other issues and milestones in the project. -->
+
+
+## Is there a test for this?
+
+* [  ] Modifies existing data-model unit test.
+* [  ] Creates new data-model unit test.
+* [  ] Modifies Xyce_Regression test.
+* [  ] Creates Xyce_Regression test.
+
+
+## Checklist
+
+* [  ] The python code is generally pep-8 compliant.
+* [  ] These changes are documented in the code.
+* [  ] These changes are documented in the developer guide/wiki.
+* [  ] These changes are documented in the user guide.
+* [  ] All new and existing test have passed.
+* [  ] No new C++ or Python warnings have been introduced.
+* [  ] These changes break backward compatibility.
+
+/label ~"Documentation"

.gitlab/merge_request_templates/FeatureRequest.md

@@ -0,0 +1,28 @@
+~"Feature Request"
+
+## Closes
+
+<!-- Which issue does this close? -->
+<!-- If there is no issue yet, create one then submit the merge request -->
+<!-- NOTE: the issue should have all info related to how the work done in this request impacts the other issues and milestones in the project. -->
+
+
+## Is there a test for this?
+
+* [  ] Modifies existing data-model unit test.
+* [  ] Creates new data-model unit test.
+* [  ] Modifies Xyce_Regression test.
+* [  ] Creates Xyce_Regression test.
+
+
+## Checklist
+
+* [  ] The python code is generally pep-8 compliant.
+* [  ] These changes are documented in the code.
+* [  ] These changes are documented in the developer guide/wiki.
+* [  ] These changes are documented in the user guide.
+* [  ] All new and existing test have passed.
+* [  ] No new C++ or Python warnings have been introduced.
+* [  ] These changes break backward compatibility.
+
+/label ~"Feature Request"

.gitlab/merge_request_templates/Task.md

@@ -0,0 +1,27 @@
+~"Task"
+
+## Closes
+
+<!-- Which issue does this close? -->
+<!-- If there is no issue yet, create one then submit the merge request -->
+<!-- NOTE: the issue should have all info related to how the work done in this request impacts the other issues and milestones in the project. -->
+
+
+## Is there a test for this?
+
+* [  ] Modifies existing data-model unit test.
+* [  ] Creates new data-model unit test.
+* [  ] Modifies Xyce_Regression test.
+* [  ] Creates Xyce_Regression test.
+
+## Checklist
+
+* [  ] The python code is generally pep-8 compliant.
+* [  ] These changes are documented in the code.
+* [  ] These changes are documented in the developer guide/wiki.
+* [  ] These changes are documented in the user guide.
+* [  ] All new and existing test have passed.
+* [  ] No new C++ or Python warnings have been introduced.
+* [  ] These changes break backward compatibility.
+
+/label ~"Task"