Initial release #46
Merged
Initial release #46
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Initial API
Update LICENSE to BSD 3
…conditions for rmse/nlopt
…m for spm+basemodel, parameterisation.py tidy
Add testing framework and non-geometric parameterisation methods
Issue templates
…ing-of-jupyter-notebooks #87 - Update notebook
This reverts commit e0cdb75.
* Return inf if simulation terminates early * Add rvs description * Update error_costs.py * Add x0 length errors * Add checks on early termination of simulation * Add test for evaluateS1 * Combine x0 length checking Co-authored-by: Brady Planden <55357039+BradyPlanden@users.noreply.github.com> * Initialise _de as float Co-authored-by: Brady Planden <55357039+BradyPlanden@users.noreply.github.com> * Add check on length of x0 * Align np.inf return type with standard return --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Brady Planden <55357039+BradyPlanden@users.noreply.github.com> Co-authored-by: Brady Planden <brady.planden@gmail.com>
…ng-due-to-npinf-cost-return
* Unpack x0, bounds and n_parameters into Cost * Pass x0, bounds and n_parameters from Cost * Remove n_parameters function check * Allow problem=None in BaseCost * Add StandaloneCost * Add test of StandaloneCosts
Update Readme & contributing
…ng-due-to-npinf-cost-return
…SOC points 3->2, Updt. CMAES boundaries creation
…d clipping with setter
…ts-are-failing-due-to-npinf-cost-return 102 - Update Pints' boundaries object
…ting-of-jupyter-notebooks Add jupyter notebook test methods
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is for an initial PyBOP release to secure the PyPI name. At the moment, the release will be a manual process following these steps:
pybop/version.pyas per the discussion belowrelease-actions.yamlshould automate the deployment to PyPIFor release versioning, I think it would be preferable to follow the
YY.MMformat. This would add clarity between PyBOP and PyBaMM releases. For reference, this release would bev23.9. Open to other thoughts though!