Sam Clarke-Green
Sam Clarke-Green
A few improvements: - [ ] remove dependency on matplotlib from core fab. Maybe move the functionality into a dedicated command line tool? - [ ] some phases do not...
After a design discussion with @MatthewHambley, we think the front-end command would benefit from command line options to set the compiler(s) with the de facto standard `$CC`, `$CXX`, and `$FC`...
During design discussions, we realised that arguments to the `fab` command could quickly become complicated and re-entering them exactly would become tedious and error prone. Our solution to this is...
This adds a feature which allows complex command line arguments to be written to a cache file and then re-used. Where an argument is specified in both the cache and...
Retire the old command line tool and its source and tests once the new one is in place
Create a new `fab` command line utility to replace the existing one. Feature list includes: - [ ] Create separate build and system loggers - [ ] Allow build and...
Add some standard flags for compiler selection, with environment variables as potential fallbacks. Adds tests for the new options and add tests for two previously untested error conditions to bring...
The current code over-uses the python exception hierarchy, especially `RuntimeError` exceptions, where custom exception classes would be better. This makes it difficult to differentiate between legitimate errors and known or...
Running the full test suite results in a psyclone test file (`tests/system_tests/psyclone/algorithm.parsable_x90`). When running interactively, this makes it appear as thought the repository has outstanding changes. This file should be...
We need a policy on whether we use relative or absolute imports for the fab modules.