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

Metadata handling in legacy Arbin software #318

Open
johnphd opened this issue Jul 18, 2024 · 0 comments
Open

Metadata handling in legacy Arbin software #318

johnphd opened this issue Jul 18, 2024 · 0 comments
Assignees
Milestone

Comments

@johnphd
Copy link

johnphd commented Jul 18, 2024

In older version of MITS PRO (Arbin) prior to the new platforms which take advantage of SQL for data management, there is a feature that is present in the software that was intended to be a feature, rather than a bug. When testing cells on an Arbin tester, one can select multiple channels to start a test schedule, the intent was to compare sets of identical cells. This has been discontinued by Arbin (I have talked to them directly) as it is not widely used.

Accidentally one can select two or more channels when starting a test. The cells can be unlike, and the schedules can be different in theory. What happens is the channel information is put into the metadata at some level which confuses the basic functions of cellpy, which seems to work fine but only when a cell is assigned to a single channel. This feature gives the appearance of the cell being assigned to multiple channels and is not processed as a result. The channel the battery is actually connected to contains data, the secondary channel which is not connected to the battery also has data, even if it is a completely different test. It could be the error originates because the secondary channel is a different battery, with a different file name creating a conflict when this is done accidentally.

This feature in the software is not used often, and these errors also do not often happen but there must be some commands to separate the metadata to avoid errors like this. I am suggesting a column that indicates the channel used, which may offer to ignore or use data. Channel information is kept anyway, this would also
cycle example
allow for redundant record keeping.

@jepegit jepegit self-assigned this Jul 24, 2024
@jepegit jepegit added this to the v.1.1.0 milestone Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants