Galvanalyser is a system for automatically storing data generated by battery cycling machines in a database

Describe the bug

Building galvanalyser_frontend
[+] Building 5.3s (14/16)
=> ERROR [build 7/7] RUN npm run build 3.9s

[build 7/7] RUN npm run build:
#14 0.768
#14 0.768 > [email protected] build
#14 0.768 > react-scripts build
#14 0.768
#14 3.085 Creating an optimized production build...
#14 3.762 Error: error:0308010C:digital envelope routines::unsupported

To Reproduce after clean install change directories in .env to match personal setup. docker-compose build

Expected behavior Build to succeed

I believe it's similar to https://github.com/webpack/webpack/issues/14532 Adding ENV NODE_OPTIONS=--openssl-legacy-provider to Dockerfile made it work for me locally

MATLAB code is not completely equal to Python code (it doesn't do column selection but does allow for extending to multiple datasets). That can be changed if we like, I suppose!

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like A clear and concise description of what you want to happen.

Additional context Add any other context or screenshots about the feature request here.

Whenever a file fails to import it seems from the worker log to be ignored the next time the harvester is run, leading to the creation for multiple harvesters to monitor the same file path.

1. Go to Harvester
2. Create Harvester
3. Import a file with bad formatting causing a fail
4. Try and rerun the harvester with the same file after fixing file formatting

Expected behavior Ideally the harvester would notice changes to the file size and rerun the import process.

The delete harvester button does not appear to work. The React component row for that harvester stays on the webpage and I think you can still run it, meaning it may not actually be deleted.

1. Got to Harvester
2. Create Harvester
3. Press Delete

Expected behavior I expect the harvester to disappear along with its datapath.

Is your feature request related to a problem? Please describe. I notice some modules are using yarn while others are using npm. This discrepancy may cause build failure in the future. Under galvanalyser frontend uses yarn in Dockerfile_dev but npm in Dockerfile. Additionally there is a yarn.lock file present in the directory which suggests Yarn is preferred. Should the prod Dockerfile be changed to use yarn?

Describe the solution you'd like To rely on one build tool. I have slight preference for Yarn but just looking for clarity and consistency

This file uses an incompatible license (copied below) to the BSD2 license used by Galavanalyser as a whole, need to resolve this

@LuAPi, you are the primary author of this, are you happy to change the license on this file to BSD2?

#!/usr/bin/env python

# =========================== MRG Copyright Header ===========================
#
# Copyright (c) 2003-2019 University of Oxford. All rights reserved.
# Authors: Mobile Robotics Group, University of Oxford
#          http://mrg.robots.ox.ac.uk
#
# This file is the property of the University of Oxford.
# Redistribution and use in source and binary forms, with or without
# modification, is not permitted without an explicit licensing agreement
# (research or commercial). No warranty, explicit or implicit, provided.
#
# =========================== MRG Copyright Header ===========================
#
# @author Luke Pitt.
#

Updated dependencies (react, MUI) and switched docker-compose.dev.yml workflow to a docker-compose.override.yml workflow. For production deployment the override file can be removed.

Is your feature request related to a problem? Please describe.

Would be great to be able to import maccor binary files as the test is progressing

Describe the solution you'd like

maccor parser currently supports text versions of maccor output files, need to extend to handle binary files

Additional context

blocker: currently can't find any information about the maccor binary file format or programs/libraries for import

The Problem: The cell data includes 7 parameters per battery name. Currently, you can only filter the datasets by cell name, which shows up as a column in datasets. You can not search datasets by battery cell parameters (e.g. cathode chemistry). This would be useful for comparing tests with common parameters.

The Solution: It would be useful to filter the datasets for the 7 parameters not present as columns in the datasets table (as adding the 7 parameters in the datasets table would make the table too busy). E.g. if I wanted to compare LFP cells, I could filter and see all the comparable datasets with this common battery cell parameter.

The problem At the moment all details in the "cells" table need to be entered separately for every cell, even if its the same make/size/type etc. as others. This is super tedious and discourages people from entering metadata.

Possible solutions One solution (maybe a quick fix) is to add a "copy" button so you can duplicate the details of another row already in the cell table but just change the cell UID. A possibly better solution would be to create a new table of "cell families" (or similar) and then the cell table would just require users to enter UIDs and then choose which cell family to associate the UID with (from a drop-down list). (Nb would need error checking to make sure the cell family already exists and if not take the user there first. Also do we check that UIDs are actually unique?? I hope so). Thinking about it, this second option is way better, because then you could compare data for all cells from a given family more easily.

Describe the bug If you don't fill in all the descriptors for cell metadata when you make a new one, e.g. anode chemistry, the API will error when trying to import cycling data with that cell metadata attached

To Reproduce Steps to reproduce the behavior:

1. create a new cell metadata
2. leave some of the options blank
3. attach metadata to a cycler test
4. import that cycler data using the python API
5. API fails

Expected behavior python will error when you run the import code

# SPDX-License-Identifier: BSD-2-Clause
# Copyright  (c) 2020-2022, The Chancellor, Masters and Scholars of the University
# of Oxford, and the 'Galvanalyser' Developers. All rights reserved.