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

Pipelining parameter sweeping for long-term degradation modelling #4277

Closed
RuiheLi opened this issue Jul 18, 2024 · 2 comments
Closed

Pipelining parameter sweeping for long-term degradation modelling #4277

RuiheLi opened this issue Jul 18, 2024 · 2 comments
Assignees
Labels

Comments

@RuiheLi
Copy link
Contributor

RuiheLi commented Jul 18, 2024

Description

This relates to a tool ParaSweeper proposed in this paper, which is mainly about pipelining parameter sweeping for long-term degradation modelling. It aims to generate large amount of long-term degradation modelling data, which can later be used for sensitivity analysis and optimization. It might be a nice feature to add on PyBaMM.

Motivation

I notice there are questions about degradation modelling on PyBaMM Discussions from time to time involving how to fit the model to ageing datasets and deal with multiple errors. This tool ParaSweeper may help a lot on those questions.
There are three useful features of ParaSweeper:

  1. Can be tailored for HPC system
  2. Run and check – always return something and not always assume the simulation runs well (all other tools assume the model runs well)
  3. Tidy up input/outputs

For these reasons, I think it can be a upgrade for the BatchStudy or Degradation experiments with reference performance tests example.

Possible Implementation

ParaSweeper has already been here. But I am happy to re-write it, break into little chunks and do whatever you may thinks that can become more compatible with PyBaMM. Any suggestions will be appreciated.

Additional context

No response

@RuiheLi RuiheLi self-assigned this Jul 18, 2024
@valentinsulzer
Copy link
Member

Open to this if it can be sufficiently generalized, but in general the PyBaMM development philosophy should be to be as model-agnostic as possible and work on things that make all models more robust. Opinionated functions that do very specific things for specific models are valuable but should live outside of the main PyBaMM repository.

@kratman
Copy link
Contributor

kratman commented Aug 27, 2024

I am going to close this for now. We can re-open it as a discussion if needed

@kratman kratman closed this as completed Aug 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants