Add a disclaimer about ITREX being discontinued#1645
Add a disclaimer about ITREX being discontinued#1645rachitchadha wants to merge 1 commit intosecurefederatedai:developfrom
Conversation
…inues. add a disclaimer at top of this notebook
| "# ⚠️ Disclaimer\n", | ||
| "\n", | ||
| "**ITREX 🛑 Discontinued** \n", | ||
| "This experiment has been discontinued. ITREX repository serves as an umbrella for IET(Intel Extension For Transformers) and neural-chat is no longer actively maintained." |
There was a problem hiding this comment.
I suggest to re-word this slightly:
This experiment is now deprecated. The ITREX repository, which serves as an umbrella for IET(Intel Extension For Transformers) and neural-chat, is no longer actively maintained.
There was a problem hiding this comment.
FYI, "ITREX" is the Intel Extension Transformers (the acronym is basically Intel Transformers Extension), so I would further simplify and reword it to:
This experiment is now deprecated. The ITREX (Intel(R) Extension For Transformers) repository is no longer actively maintained.
|
Please sign your commits by running |
|
If ITREX / Neuralchat libraries are archived, they should be removed from the example. From looking through the notebook I expect it's straightforward to swap in other Huggingface libraries here, but I'll defer to @kta-intel if he has a different recommendation as this is his original example |
Yeah, it should be fairly straightforward to swap ITREX calls with HF Transformer calls, but I actually recommend we remove this example entirely. As it stands, without the ITREX components (which I agree should be removed since they are archived), this example won't add any unique functionalities from the phi-4 fine-tuning example WDYT? @teoparvanov @rachitchadha |
Add a disclaimer at top of this notebook that Umbrella repo containing IET and neural-chat (ITREX) has been discontinued
Summary
[Provide a short and descriptive summary of the pull request, e.g., "Improve caching mechanism for API calls"]
Type of Change (Mandatory)
Specify the type of change being made.
Description (Mandatory)
[Explain the goal of this PR, the problem it solves and a summary of changes made. Reference any related issues or tickets (e.g.,
Fixes #123).]Testing
[Describe the testing done for this PR. If applicable include screenshots.]