Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add creating_a_problem example #487

Open
wants to merge 5 commits into
base: develop
Choose a base branch
from

Conversation

f-g-r-i-m-m
Copy link

Description

added the creating_a_problem example. This example builds up on the creating_a_model example.

Type of change

  • New Feature: A non-breaking change that adds new functionality.
  • Optimization: A code change that improves performance.
  • Examples: A change to existing or additional examples.
  • Bug Fix: A non-breaking change that addresses an issue.
  • Documentation: Updates to documentation or new documentation for new features.
  • Refactoring: Non-functional changes that improve the codebase.
  • Style: Non-functional changes related to code style (formatting, naming, etc).
  • Testing: Additional tests to improve coverage or confirm functionality.
  • Other: (Insert description of change)

Key checklist:

  • No style issues: $ pre-commit run (or $ nox -s pre-commit) (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
  • All unit tests pass: $ nox -s tests
  • The documentation builds: $ nox -s doctest

You can run integration tests, unit tests, and doctests together at once, using $ nox -s quick.

Further checks:

  • Code is well-commented, especially in complex or unclear areas.
  • Added tests that prove my fix is effective or that my feature works.
  • Checked that coverage remains or improves, and added tests if necessary to maintain or increase coverage.

Thank you for contributing to our project! Your efforts help us to deliver great software.

Grimm and others added 2 commits September 9, 2024 13:38
Added an example for how to create a problem. The example builds up on the creating_a_model example.
Copy link

codecov bot commented Sep 9, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.04%. Comparing base (3eef641) to head (4e60d8f).
Report is 205 commits behind head on develop.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #487   +/-   ##
========================================
  Coverage    99.04%   99.04%           
========================================
  Files           52       52           
  Lines         3545     3545           
========================================
  Hits          3511     3511           
  Misses          34       34           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@BradyPlanden
Copy link
Member

Excellent, thanks for this @f-g-r-i-m-m! I'll take a further look over the next day or so.

Copy link
Member

@BradyPlanden BradyPlanden left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this addition @f-g-r-i-m-m, it's coming along well. A few suggestions and comments to address from my side.

examples/notebooks/creating_a_problem.ipynb Outdated Show resolved Hide resolved
examples/notebooks/creating_a_problem.ipynb Outdated Show resolved Hide resolved
examples/notebooks/creating_a_problem.ipynb Outdated Show resolved Hide resolved
"metadata": {},
"source": [
"### Testing the problem\n",
"To verify our problem, we solve assign a sum of squared error cost function to it and solve it. \n",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would first show how to use the problem.evaluate() and problem.evaluateS1 methods.

examples/notebooks/creating_a_problem.ipynb Show resolved Hide resolved
"metadata": {},
"source": [
"### Setting up the problem\n",
"With all parts setup, we can now make a problem. Therefore, we use pybop.FittingProblem() to define a simple fitting problem and the model, parameters and dataset defined before as inputs."
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you also expand this to include the pybop.DesignProblem? I think we can reduce the cost / optimisation side of this and focus on the two problem classes more.

examples/notebooks/creating_a_problem.ipynb Show resolved Hide resolved
examples/notebooks/creating_a_problem.ipynb Show resolved Hide resolved
examples/notebooks/creating_a_problem.ipynb Show resolved Hide resolved
"source": [
"## Creating a Problem\n",
"\n",
"In this notebook, we create and solve a single particle model (SPM). This is achieved using a predefined parameter set introduced in Marquis et al. [[1]](https://doi.org/10.1149/1945-7111/abbce4) \n",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needs an update to introduce the problem class and it's functionality.

f-g-r-i-m-m and others added 3 commits October 7, 2024 12:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants