Noctam/DWP/ACS Test Harness/Diary/Week 1: Difference between revisions
Jump to navigation
Jump to search
First cut of first week |
|||
| Line 32: | Line 32: | ||
checks of the config value starts with '../' and replaces '../' with the | checks of the config value starts with '../' and replaces '../' with the | ||
root folder provided by getrootfolder()) when it loads the config. | root folder provided by getrootfolder()) when it loads the config. | ||
* Stepped it through a DCI913 call to get an idea of a) what it did, and b) how it did it. My [[Noctam/DWP/ACS Test Harness/Notes#CISSIM|notes]] are available, for now, but in a nutshell: | |||
{{quote|OK, this is actually quite flexible, and, although the code is terse and uncommented, it's not that hard to follow. Ultimately, it doesn't do that much (in the above, quite narrow, use case) - I could fairly easily strip out everything that isn't required by a DCI call and just have that as our starting block of code... I might do that, though I want to get PDD and NPS in there too, neither of which are handled in my initial examination above. }} | |||
Revision as of 16:45, 7 September 2021
| ACS Test Harness |
|---|
|
Meetings Existing System Specifications Diary |
Day 1
06/06/2021
Initial workshop to discuss requirements and broad development strategy. See Meetings: Initial Workshop.
Day 2
07/09/2021
In which I:
- installed and set up intellij + python on my noctam PC
- created simplistic
sim-startandsim-stopscripts to start and stop the CISSIM server - got it up and running, which required a bit of jiggery-pokery:
- needed to install
windows-cursesin my python environment:pip install windows-curses - Fixed a couple of relative paths hardcoded into a couple of python files. To wit:
- needed to install
commit 5205c969edcfe9e075ca8261a3ca2f13fa3e7129 Author: Stuart Wood (Noctam) <stuart.wood@noctam.co.uk> Date: Tue Sep 7 14:34:42 2021 +0100 Don't rely on relative paths for files/folders Adds a 'getrootfolder' function to pdutils which gets the root folder of the 'project', by getting the parent of the directory in which the pdutils file is found. I can't immediately think of any problem with this, and it means you can run it safely from anywhere. This also dynamically alters the 'FOLDERS' config value (actually it checks of the config value starts with '../' and replaces '../' with the root folder provided by getrootfolder()) when it loads the config.
- Stepped it through a DCI913 call to get an idea of a) what it did, and b) how it did it. My notes are available, for now, but in a nutshell:
OK, this is actually quite flexible, and, although the code is terse and uncommented, it's not that hard to follow. Ultimately, it doesn't do that much (in the above, quite narrow, use case) - I could fairly easily strip out everything that isn't required by a DCI call and just have that as our starting block of code... I might do that, though I want to get PDD and NPS in there too, neither of which are handled in my initial examination above.