Faraday tech sessions

We have two session in the Faraday Tech Series:

Tues 2nd June 10:00-11:30. Python Battery Mathematical Modelling (PyBaMM) Part 1: Demonstrating the basics of PyBaMM and how you can use it. Register here: PyBaMM, Part 1

Tues 9th June 10:00-11:30. Demonstrating more advanced features of PyBaMM. Register here: PyBaMM, Part 2 In this session we will demonstrate the speed and flexibility of PyBaMM through a series of case studies, followed by a Q&A discussion on how to utilise PyBaMM in your research.

The idea is the first of these will basically be a condensed version of the user workshop and the second will be more in depth with some case studies. I think it makes sense to do a new release before this.

Possible timetable could be:

2nd June 10:00-10:05 - show how to install/point to website 10:05-10:20 - pybamm overview (explain motivation/core idea. show off functionality and give an outline for this and the next session) 10:20-10:55 - running a simulation, running an experiment, plotting etc. 10:55-11:15 - changing parameters, settings etc. 11:15-11:30 - questions/discussion

9th June 10:00-10:05 - intro/welcome 10:05-11:00 - case studies (@ferranbrosa @TomTranter ?) 11:00 - 11:15 - workflow for contributing
11:15-11:30 discussion

I’m happy to do the first session (unless anyone wants to volunteer for parts of it!), but it would be good if some others could be online to help troubleshoot/answer questions live. The plan is to run on teams/slack as before.

Things to include in release

• update parameters cli so you can grab an entire directly (just so it is easy for users to see e.g. all lithium-ion parameters in their local directory)
• interactive plot (#985) might be nice, but not essential
• should we add a dimensional “basic” DFN model so that people who aren’t familiar with non-dimensionalisation can hack away at it? could even define params locally to show how to truly do thing self-contained, though maybe this is best left as a separate example (by this I mean explicitly doing a = pybamm.Parameter("name") rather than using pybamm.standard_parameters, I think having the actual values defined in the script too might be too much)
• ???

[rtimms]

should we do #920 before this, just so that all user interfaces are in dimensional form?

[rtimms]

ok. I think we probbaly don’t want to go down the route of showing how the equations are non-dimensionalised in the workshop, just point out that the models in pybamm are dimensionless. Then point out we have the dimensional “basic” there for people to use if they wish. This won’t have the flexibility of the submodel structure, but a possible workflow for people learning/contributing who aren’t familiar with non-dim is -> follow/edit “basic” model to do what they want -> ask us for help with non-dim after -> ask for help turning their new addition into a submodel which fits into the structure. Hopefully as we get more users there will be more people that can be asked for help at each stage and the burden on us will be smaller.