Closed SynbioLucas closed 8 years ago
As indicated, RAM and program memory would be an issue, since they were already maxed out when I finished programming.
IF this is possible, however, would it make more sense to have the calibration values in a different file than the lpf file? and make the calibration (currently matlab) script generate this file.
I agree that it makes a lot of sense to have this be a separate file, which is produced by the calibration script. If we were to implement this, we'd want to think about if we want to have a way to paste these into LPI somewhere or if people would just have to upload a file every time (non-ideal). But this isn't really an issue at the moment since we don't even know if this will be possible.
The best reason for decoupling the LPF and the calibration data is that you may want to transmit/share an LPF file to someone else or to another device, but the calibration settings wouldn't be useful or valid for that other person and their other device.
First, we see if it's worth thinking about at all...
On Mon, Sep 14, 2015 at 3:32 PM Sebastian M. Castillo Hair < notifications@github.com> wrote:
As indicated, RAM and program memory would be an issue, since they were already maxed out when I finished programming.
IF this is possible, however, would it make more sense to have the calibration values in a different file than the lpf file? and make the calibration (currently matlab) script generate this file.
— Reply to this email directly or view it on GitHub https://github.com/rice-bioe/LPI/issues/192#issuecomment-140197421.
@castillohair Have you had a chance to think about this much lately? We're getting close to the time where we have to commit one way or another on how calibrations will be set in the devices.
cc @KarlGerhardt
No, but I'll definitely get to it starting tomorrow, and hopefully end by the weekend.
Update: @castillohair says that this will likely be possible, but he won't know for sure until it's fully implemented.
@castillohair Has implemented this! Therefore, it is both closed and not an Iris issue.
It would be a vast improvement to the workflow to only have to flash the firmware to a device once and to have the calibration settings (DC/GS) settings read from the SD card. SMC isn't sure if this is possible since there isn't any program memory or RAM available for this improvement. He agreed to look into the code again briefly to see if this is possible, but we shouldn't hold our breaths.