Adds configuration file parsing capabilities including locating the file in the repo given a name, generating flows, and generating actual commands.
Details
Assumptions
Config files are expected to be in the software\configs folder
Config files must be JSON files (end with .json)
Config files can't have any comments (i.e. no #), this is something dictated by the JSON format
Config p
File Updates
main.py: can pass a config file and have it parsed to generate commands. Note: nothing is done with these commands yet.
\util\config_parser.py: locates the file, generates a flow, and generates commands for the overall file
\util\experiments.py: generates commands for specific expereiment sub-type (sweepFreq etc.) used by config_parser
\tests\test_config_parser.py and test_experiments.py: pytest unit test for config_parser.py and experiment.py
\configs: contains config files
Running
Main runs very similar to before except that passing in a config file is optional. If a config file is passed in main will try to parse it and generate commands, otherwise it will produce an error that shuts down the program. Main still tries to connect to devices and prompts the user for commands to send to devices.
20
Overview
Adds configuration file parsing capabilities including locating the file in the repo given a name, generating flows, and generating actual commands.
Details
Assumptions
File Updates
Running
Main runs very similar to before except that passing in a config file is optional. If a config file is passed in main will try to parse it and generate commands, otherwise it will produce an error that shuts down the program. Main still tries to connect to devices and prompts the user for commands to send to devices.