Next Steps with SDS

[ReinhardKeil]

Scope:

• Focus on Playback: enable regression tests on HW (Alif E8) and FVP

  • Use only FVP versions without Phyton version binding
  • RTT is used for system analysis and should show workload distribution, wait states (i.e. cause by Cache misses, etc.)
  • FVP is used to verify correctness in MLOps system (without actual target hardware).

• EW example with ModelNova (ExecuTorch) on Alif A8 with CM55+Ethos-U55 or CM55+Ethos-U85

  • Maps to SSE-300 or SSE-320

Recommendations:

• AVH will be paused. Only VSI3 will be productized in SDS-Framework

  • Configuration file for SDSIO VSI (as a later step in SDSIO Server) #145

• Introduce concept for SDS file data labeling (allow renaming of SDS files effectively with format <sds-pipe>.<label>.sds

  

• For playback, introduce a sdsio.yml control file for sdsio-server and vsi3, for example:

play-dir: <name>           # directory that holds SDS files for playback
rec-dir: <name>            # directory for SDS file recording output
play-list:                 # list of files for playback (default: all files of play-dir are used)
  - Scinput.0+LabelA.sds
  - Scinput.0+LabelB.sds

• Play and Record files should have always the same <label>. A SDS recording file that is overwritten will create a *.bak file, i.e. <sds-pipe>.<label>.sds.bak. A previous *.bak file is deleted.

Related:

• CI flow should verify DataOutput files #161

[MiloradCvjetkovic]

I suggest we specify a pattern for playback with the following syntax
[<rel_path>/][<filename_prefix>]{stream_name}[<filename_suffix>]

Parameters

• [<rel_path>/] specifies path relative to root_dir
• [<filename_prefix>] specifies filename prefix
• {stream_name} is the parameter of the sdsPlayOpen operation
• [<filename_suffix>] specifies filename suffix

Remarks
Parameters except {stream_name} can use the wildcard character, *, to substitute for any string of characters.

Behavior
After first sdsPlayOpen operation the first found filename matching the pattern is registered and all further sdsRecOpen/sdsPlayOpen operations use the registered filename and replace the {stream_name} with the stream name provided in the sdsRecOpen/sdsPlayOpen operation.
After all streams are closed, upon new sdsPlayOpen operation, next file matching pattern is searched for and the procedure repeats.
After all files matching first pattern are exhausted the process repeats using the next pattern from the file-pattern-list.
This list is ignored if no playback operations are used, so for just recording the procedure with auto-incrementing indexes is used.
If the matching file for recording already exists the extension .bak is added to it and new file with same name is created.

Example of such .yml file

root_dir: <path>                               # root directory
play-pattern-list:                             # list of patterns for playback
  - Rock0/{stream_name}.0.sds
  - Rock1/{stream_name}.0.sds
  - Rock2/{stream_name}.0.sds
  - Paper*/{stream_name}.0.sds
  - New/Rock*/{stream_name}.0.sds
  - Scissors0_{stream_name}.*.sds
  - Scissors*_{stream_name}.*.sds
  - {stream_name}_Scissors0.sds
  - {stream_name}+Scissors0.sds
  - {stream_name}-Scissors0.sds