in this repo, there are several places where images and other binary files, are used (even multiple times). thus, why not make a method in klib to access them and use them directly through code, rather than copy/pasting these files every time you wanna try out something new.
files should be available via:
[x] Path to each file (ex: */codefiles/lib/data/baby.png)
[x] As relevant object directly through code (klib.getBabyImage() -> {returns numpy object})
OPTIONAL:
[ ] perhaps have a wrapper file that lets you create and delete files on the fly so they can be removed when the code is finished with them.
in this repo, there are several places where images and other binary files, are used (even multiple times). thus, why not make a method in klib to access them and use them directly through code, rather than copy/pasting these files every time you wanna try out something new.
files should be available via:
[x] Path to each file (ex: */codefiles/lib/data/baby.png)
[x] As relevant object directly through code (klib.getBabyImage() -> {returns numpy object})
OPTIONAL: