initial commit

Co-authored-by: stfleming <[email protected]>
Co-authored-by: skalade <[email protected]>
Co-authored-by: mariodruiz <[email protected]>
Co-authored-by: cathalmccabe <[email protected]>
Co-authored-by: plysaght <[email protected]>
Co-authored-by: npurusho <[email protected]>
Co-authored-by: jogomojo <[email protected]>
Co-authored-by: haandradeb <[email protected]>
Co-authored-by: andrewgschmidt <[email protected]>
Co-authored-by: joshual-xlnx <[email protected]>

Author: 11 people

.gitattributes

@@ -0,0 +1,53 @@
+# Per default everything gets normalized and gets LF line endings on checkout.
+* text eol=lf
+*.txt eol=lf
+*.md eol=lf
+*.html eol=lf
+*.cpp eol=lf
+*.hpp eol=lf
+*.h eol=lf
+*.c eol=lf
+*.cc eol=lf
+
+# These will always have CRLF line endings on checkout.
+*.vcxproj text eol=crlf
+*.props text eol=crlf
+*.project text eol=crlf
+*.cproject text eol=crlf
+*.inf text eol=crlf
+*.lic text eol=crlf
+
+# These are binary so should never be modified by git.
+*.exe binary 
+*.png binary
+*.jpg binary
+*.jpe binary
+*.jpeg binary
+*.JPG binary
+*.PNG binary
+*.gif binary
+*.ttf binary
+*.eot binary
+*.woff binary
+*.inv binary
+*.dxf binary
+*.mp4 binary
+*.wav binary -crlf
+*.mp3 binary
+*.hdf binary
+*.bat binary
+*.pdm binary
+*.doctree binary
+*.elf binary -crlf
+*.bin binary -crlf
+*.bit binary -crlf
+*.a binary -crlf
+*.bsp binary
+*.dll binary
+*.pyd binary
+*.so binary
+*.whl binary
+*.xclbin binary
+*.zip binary
+*.pt binary
+*.onnx binary

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Support Forum
+    url: https://github.com/AMDResearch/Riallto/discussions
+    about: Request community support

.github/ISSUE_TEMPLATE/issue_template.yml

@@ -0,0 +1,73 @@
+name: Notebook Issue Report
+description: File an issue report
+title: "[Notebook Issue]: "
+labels: ["Issue"]
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to report an issue!
+  - type: checkboxes
+    attributes:
+      label: Is there an existing [issue](https://github.com/AMDResearch/Riallto/issues) or [discussion](https://github.com/AMDResearch/Riallto/discussions) related to your problem?
+      description: Please search to see if an issue already exists for this.
+      options:
+      - label: I have searched the existing issues
+        required: true
+  - type: dropdown
+    id: notebook
+    attributes:
+      label: Notebook
+      description: What notebook are you having issues with?
+      options:
+        - 1_0_Introduction.ipynb
+        - 1_1_ryzenai.ipynb
+        - 2_1_MS_Windows_Studio_Effects.ipynb
+        - 3_1_Color_threshold_example.ipynb
+        - 3_2_Ryzenai_capabilities.ipynb
+        - 3_3_Scaled_color_threshold_example.ipynb
+        - 3_4_Edge_detect_example.ipynb
+        - 3_5_Color_detect_example.ipynb
+        - 4_1_software_framework.ipynb
+        - 4_2_write_your_kernel.ipynb
+        - 4_3_kernels_with_runtime_parameters.ipynb
+        - 4_4_threshold_kernel_with_vector_ops.ipynb
+        - 4_5_describe_an_application.ipynb
+        - 4_6_build_application.ipynb
+        - 4_7_using_the_memtile_in_your_applications.ipynb
+        - 4_8_build_a_colorDetect_application.ipynb
+        - 5_1_pytorch_onnx_inference.ipynb
+        - 5_2_pytorch_onnx_re-train.ipynb
+        - Appendix_Review_of_Image_Processing_Concepts.ipynb
+        - Glossary.ipynb
+    validations:
+      required: true
+  - type: textarea
+    id: section
+    attributes:
+      label: Section
+      description: |
+        Please describe in which section you are having problems
+
+        Tip: Copy the section name directly from the notebook
+      render: markdown
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Please describe the problem(s) you are facing
+      render: markdown
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Anything else?
+      description: |
+        Anything else that you would like to include?
+
+        Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in. If you are adding code, we suggest you use [code snippets](https://docs.github.com/en/github/writing-on-github/creating-and-highlighting-code-blocks).
+    validations:
+      required: false

.github/pull_request_template.md

@@ -0,0 +1,21 @@
+<!-- Thanks for taking the time to submit a pull request! Please fill out below, remove sections that don't apply for your pull request.  -->
+
+### Describe the problem solved by the commit
+
+### How is the problem solved?
+
+### Are there any risks associated to the change?
+
+### Is there a documentation impact?
+
+### Checklist
+
+<!-- We suggest you run all the pytests and report the output. Put an `x` in the boxes that apply -->
+
+- [ ] I added a test to cover my changes
+- [ ] Existing and new test pass
+- [ ] I read and I accept the [CONTRIBUTING.md](https://github.com/AMDResearch/Riallto/blob/main/CONTRIBUTING.md) guidelines
+
+### Please provide screenshots (if applicable)
+
+### Related issues

.gitignore

@@ -0,0 +1,13 @@
+# Python cache files
+######################
+__pycache__/
+
+
+# WSL build files
+######################
+install/temp
+install/tests
+install/installed
+install/tarballs/*.tar.gz
+
+*-checkpoint.ipynb

CONTRIBUTING.md

@@ -0,0 +1,66 @@
+# Contributing to Riallto
+
+We welcome contributions to Riallto - please see our guidelines below for preparing your pull request.  
+
+## 1. Submit your patch using a pull request
+
+Please use GitHub Pull Requests for sending code contributions. When sending code sign your 
+work as described below. Be sure to use the same license for your contributions as the current 
+license of the Riallto.
+
+## 2. Sign your work
+
+Please use the *Signed-off-by* line at the end of your patch which indicates that you accept the Developer Certificate of Origin (DCO) defined by https://developercertificate.org/ reproduced below::
+
+```
+  Developer Certificate of Origin
+  Version 1.1
+
+  Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
+  1 Letterman Drive
+  Suite D4700
+  San Francisco, CA, 94129
+
+  Everyone is permitted to copy and distribute verbatim copies of this
+  license document, but changing it is not allowed.
+
+
+  Developer's Certificate of Origin 1.1
+
+  By making a contribution to this project, I certify that:
+
+  (a) The contribution was created in whole or in part by me and I
+      have the right to submit it under the open source license
+      indicated in the file; or
+
+  (b) The contribution is based upon previous work that, to the best
+      of my knowledge, is covered under an appropriate open source
+      license and I have the right under that license to submit that
+      work with modifications, whether created in whole or in part
+      by me, under the same open source license (unless I am
+      permitted to submit under a different license), as indicated
+      in the file; or
+
+  (c) The contribution was provided directly to me by some other
+      person who certified (a), (b) or (c) and I have not modified
+      it.
+
+  (d) I understand and agree that this project and the contribution
+      are public and that a record of the contribution (including all
+      personal information I submit with it, including my sign-off) is
+      maintained indefinitely and may be redistributed consistent with
+      this project or the open source license(s) involved.
+```
+
+Here is an example Signed-off-by line which indicates that the contributor accepts DCO:
+
+```
+  This is my commit message
+
+  Signed-off-by: Jane Doe <[email protected]>
+```
+
+## 3. We will review your contribution
+
+If any additional fixes or modifications are necessary, we may provide feedback to guide 
+you. When accepted, your pull request will be merged to the repository.