Currently the Configuration Table we are parsing coefficients from is located in our Capstone Google Drive, which may not exist within a handful of years as our student accounts are (hopefully) deleted by IT. The config table should either be moved to the DAQ Google Drive or some other long term location.
The most basic version of this would be as simple as swapping out an api key and getting Berube or someone else with permission to upload the file, but I think there are some improvements that could be made on the config_fetch module and config table itself to make it easier to make more parts of the pre processing system configurable.
May also need to flag the config table in the folder so it doesn't get deleted automatically by google for inactivity, but we could do a pull from it once a month or something to avoid that possibility I think.
Currently the Configuration Table we are parsing coefficients from is located in our Capstone Google Drive, which may not exist within a handful of years as our student accounts are (hopefully) deleted by IT. The config table should either be moved to the DAQ Google Drive or some other long term location.
The most basic version of this would be as simple as swapping out an api key and getting Berube or someone else with permission to upload the file, but I think there are some improvements that could be made on the config_fetch module and config table itself to make it easier to make more parts of the pre processing system configurable.
May also need to flag the config table in the folder so it doesn't get deleted automatically by google for inactivity, but we could do a pull from it once a month or something to avoid that possibility I think.