Scale down image #77
Merged
Scale down image #77
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Removing windows python bindings Remove check from linux for now Dropping down to python3.8 for mlir-aie compatibility in the same env. Still having issues not being able to find the CU name in the xclbin when loading the application commented out state check as it is not working with linux driver (different pyxrt bindings needed?) Call the script to run unregistered xclbins before in the apprunner init Copy headerfiles one by one, on linux subprocess isn't liking the wildcards. Now checks to see if it is a windows filepath rather that just running on windows when doing path translations. Added a simple test to test various path types. Getting tests up and running on linux Changes to arguments to get the latest NPU linux driver working Rebuilding all the prebuilt applications with the patched version of MLIR-AIE for linux Stopping nputop erroring out for now Attempting to bump linux support to py3.10 bumping pyxrt to 310 bindings (thanks Sarunas) Falling back to older driver version for RyzenAI SW Linux tests Constraining the appropriate python version based on platform. Signing does not need to happen on windows based flows, so adding a check. Also, keeping the error status check after an apprun for windows but this does not currently work with the bindings on linux. Reintroducing the windows python bindings alongside the linux one Added docker setup for Riallto Linux Keep stability check in for Windows Case matters for linux which caught this issue.
* Add citation file * Shane's orcid
…an Ubuntu 24.04 system from scratch
* Fix link to Ryzen AI webpage (AMDResearch#31) * extra symbols to wsl path resolution (AMDResearch#10) * Latest version of numpy causing issues, constraining it to v1.* (AMDResearch#35) * Latest version of numpy causing issues, constraining it to v1.* * readability fix * Enable Kernel fusion (AMDResearch#34) * Include library of kernels in the compilation * Fix typos * Include kernels header file * Prepare kernels for superkernel * Include test name * Initial superkernel test * Simplyfy test * Add second superkernel * Rename test to better reflect the nature of PR * Rename test to better reflect the nature of PR * Align code * Fix call * More fixes * Remove fake kernels * Kernel fusion working!!!! * Fix duplicate variable name * Add another test * Remove unnecesary flag * Remove * revert to original * Revert to original * Revert to original * Revert to original * Include kernels * Copy kernel * Import shutil * Allow to load the same Riallto app up to 4 times (AMDResearch#36) * Allow multiple instances of the same app to be run * Try to fix test * Add more tests * Flake8 * More appropiate test name * Make sure AppRunner has device, device is not found is previous call had an space issue * Made code more pythonic * Handle AppRunner object even if it fails * Flake8 * Report app start column (AMDResearch#37) * Allow multiple instances of the same app to be run * Try to fix test * Add more tests * Flake8 * More appropiate test name * Make sure AppRunner has device, device is not found is previous call had an space issue * Made code more pythonic * Handle AppRunner object even if it fails * Flake8 * Try to add start column * Add starting column * Flake8 * Update check * Fix where assert is done * Fix issue with counting * Check that xbutil count is working * Do not run xbutil test for Linux * Add missing os import * Skip test in Linux --------- Co-authored-by: Sarunas Kalade <[email protected]> Co-authored-by: Shane Fleming <[email protected]>
… an argument. Also added waits after the docker container stop commands to prevent race conditions when attempting to start the next container instance.
* Notebook update to factor in Linux support * Addressing some of Mario's feedback * Added the cell outputs * Pushing correct notebook where outputs should be left in * Added command to check the kernel version on Linux * Stop it from blocking jupyter lab from starting if no webcam is connected
* Add test to check data parallel with non tested buffer names * Fix memory tile animations for buffers that have name different than in_buffer * Do not track svg files * Update year * Move function to the top * Add more automatic tests * Attempt to fix buffer representation * Fix checks * Fix token generation * Intermediate update * Fix visualization for passthrough mode * Improve quality of tests * Add randomness to the buffers name to make sure nothing is hardcode * Add more files to ignore only in current folder * Add buffer when data comes from non neighbor * Fix asserts * Add checks * Start in a different place
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe the problem solved by the commit
In the remote lab sometimes the latency is large when full images are displayed on the notebook
How is the problem solved?
Reduce the size of the video feed displayed using the scale argument
Are there any risks associated to the change?
No
Is there a documentation impact?
No