First impressions on pulling up the GUI:

When I first open the "Battery Voltage" pane, the first entry for Cell cutoff voltage looks like an input:

but then as soon as I mouse over it, it changes to calculated:

We can talk more about Qfull after cutoff implementation and the calculated cell cutoff voltage field at the meeting.

I noticed you updated the defaults, which is good, but battery parameters that vary with chemistry are also in JSON files that are loaded when the chemistry changes. Should cutoff voltage be added to these files?

Should the cutoff voltage be greyed out when the voltage table is used? It might make sense to move these to "electrochemical properties" rather than "voltage properties"

First impressions on pulling up the GUI:

When I first open the "Battery Voltage" pane, the first entry for Cell cutoff voltage looks like an input:

but then as soon as I mouse over it, it changes to calculated:

We can talk more about Qfull after cutoff implementation and the calculated cell cutoff voltage field at the meeting.

I noticed you updated the defaults, which is good, but battery parameters that vary with chemistry are also in JSON files that are loaded when the chemistry changes. Should cutoff voltage be added to these files?

Should the cutoff voltage be greyed out when the voltage table is used? It might make sense to move these to "electrochemical properties" rather than "voltage properties"

I noticed the first issue yesterday it's an issue with the initialization in my callback script that I still need to fix. And how the value is defined is up for discussion as well. Right now, unchecked should display a calculated value of 0.66*Vnom, while checked should change to an input where the user inputs the cutoff voltage.

I wasn't aware of those JSON files for the battery parameters so I'd refer to your judgement on that. The behavior for the voltage table was one of my discussion points for the meeting.