Develop (#1)

* Remove stock env.

* Remove text-intel-torch.yml

* Add intel_env.yml

* Update quantize_inc_gpt2.py

-Fix broken instructions.

* Update generate_text.py

-Add xpu compatibility.

* Add .gitignore

* Remove inference-transformers.png

* Remove E2E_stock-transformers.png

* Remove intel flag from finetune_model.py

* Add kaggle to intel_env.yml

* Update README.md

- Remove stock references
- Correct style
- Redistribute information
- Add Introduction
- Add Solution Technical Overview
- Add Solution Technical Details
- Add Validated Hardware Details
- Add How it Works
- Add Get Started
- Add Supported Runtime Environment
- Add Summary and Next Steps
- Add Appendix

* Remove README.md from data directory

* Update SECURITY.md file

* Update intel_env.yml file

- Add gperftools to dependencies.

* Remove config_finetuned.yml

* Move prompt.csv to config dir

* Add gpt_generate_text.py file

* Add files to patch transformers to use xpu.

* Added logger to gptj_generate_text.py

* Update README.md

- Correct styles
- Fix typos
- Add sections
- Format commands

* Fix bfloat16 RuntimeError

* Update intel_env.yml dependencies

* Update transformers_xpu.patch

* Updated license year to 2024

* Remove xpu dependency from intel_env.yml

* Create intel_env_xpu.yml
- Differs with intel_env.yml by including a  intel-extension-for-pytorch version capable of using XPU.

* Add instructions to use XPU to README.md

* Make typo and corrections to instructions for README.md

* Add blank space line at EOF

* Remove inconsistent sentence from README.md

Author: aagalleg

.gitignore

@@ -0,0 +1,143 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+data/
+output/
+saved_models
+nc_workspace
+.vscode

LICENSE

@@ -1,4 +1,4 @@
-Copyright (c) 2023, Intel Corporation
+Copyright (c) 2024, Intel Corporation
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are met:

README.md

@@ -1,5 +1,7 @@
 # Security Policy
-Intel is committed to rapidly addressing security vulnerabilities affecting our customers and providing clear guidance on the solution, impact, severity and mitigation. 
+
+Intel is committed to rapidly addressing security vulnerabilities affecting our customers and providing clear guidance on the solution, impact, severity and mitigation.
 
 ## Reporting a Vulnerability
-Please report any security vulnerabilities in this project utilizing the guidelines [here](https://www.intel.com/content/www/us/en/security-center/vulnerability-handling-guidelines.html).
+
+Please report any security vulnerabilities in this project [utilizing the guidelines here](https://www.intel.com/content/www/us/en/security-center/vulnerability-handling-guidelines.html).