arize-phoenix 0.0.39__tar.gz → 0.0.41__tar.gz

{arize_phoenix-0.0.39 → arize_phoenix-0.0.41}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: arize-phoenix
-Version: 0.0.39
+Version: 0.0.41
 Summary: ML Observability in your notebook
 Project-URL: Documentation, https://docs.arize.com/phoenix/
 Project-URL: Issues, https://github.com/Arize-ai/phoenix/issues
@@ -82,16 +82,16 @@ Description-Content-Type: text/markdown
 
 Phoenix provides MLOps and LLMOps insights at lightning speed with zero-config observability. Phoenix provides a notebook-first experience for monitoring your models and LLM Applications by providing:
 
--   **LLM App Tracing** - Trace through the execution of your LLM Application to understand the internals of your LLM Application and to troubleshoot problems related to things like retrieval and tool execution.
+-   **LLM Traces** - Trace through the execution of your LLM Application to understand the internals of your LLM Application and to troubleshoot problems related to things like retrieval and tool execution.
 -   **LLM Evals** - Leverage the power of large language models to evaluate your generative model or application's relevance, toxicity, and more.
 -   **Embedding Analysis** - Explore embedding point-clouds and identify clusters of high drift and performance degradation.
--   **RAG Introspection** - Visualize your generative application's search and retrieval process to solve improve your retrieval augmented generation.
+-   **RAG Analysis** - Visualize your generative application's search and retrieval process to solve improve your retrieval-augmented generation.
 -   **Structured Data Analysis** - Statistically analyze your structured data by performing A/B analysis, temporal drift analysis, and more.
 
 **Table of Contents**
 
 -   [Installation](#installation)
--   [LLM App Tracing](#llm-app-tracing)
+-   [LLM Traces](#llm-traces)
     -   [Tracing with LlamaIndex](#tracing-with-llamaindex)
     -   [Tracing with LangChain](#tracing-with-langchain)
 -   [LLM Evals](#llm-evals)
@@ -99,7 +99,7 @@ Phoenix provides MLOps and LLMOps insights at lightning speed with zero-config o
     -   [UMAP-based Exploratory Data Analysis](#umap-based-exploratory-data-analysis)
     -   [Cluster-driven Drift and Performance Analysis](#cluster-driven-drift-and-performance-analysis)
     -   [Exportable Clusters](#exportable-clusters)
--   [RAG Introspection](#rag-introspection)
+-   [Retrieval-Augmented Generation Analysis](#retrieval-augmented-generation-analysis)
 -   [Structured Data Analysis](#structured-data-analysis)
 -   [Community](#community)
 -   [Thanks](#thanks)
@@ -119,7 +119,7 @@ Some functionality such as LLM evals are under the `experimental` subpackage.
 pip install arize-phoenix[experimental]
 ```
 
-## LLM App Tracing
+## LLM Traces
 
 ![LLM Application Tracing](https://github.com/Arize-ai/phoenix-assets/blob/main/gifs/langchain_rag_stuff_documents_chain_10mb.gif?raw=true)
 
@@ -129,7 +129,7 @@ With the advent of powerful LLMs, it is now possible to build LLM Applications t
 
 [![Open in Colab](https://img.shields.io/static/v1?message=Open%20in%20Colab&logo=googlecolab&labelColor=grey&color=blue&logoColor=orange&label=%20)](https://colab.research.google.com/github/Arize-ai/phoenix/blob/main/tutorials/tracing/llama_index_tracing_tutorial.ipynb) [![Open in GitHub](https://img.shields.io/static/v1?message=Open%20in%20GitHub&logo=github&labelColor=grey&color=blue&logoColor=white&label=%20)](https://github.com/Arize-ai/phoenix/blob/main/tutorials/tracing/llama_index_tracing_tutorial.ipynb)
 
-![LLM App Tracing UI](https://storage.googleapis.com/arize-assets/phoenix/assets/images/trace_details_view.png)
+![LLM Traces UI](https://storage.googleapis.com/arize-assets/phoenix/assets/images/trace_details_view.png)
 
 To extract traces from your LlamaIndex application, you will have to add Phoenix's `OpenInferenceTraceCallback` to your LlamaIndex application. A callback (in this case an OpenInference `Tracer`) is a class that automatically accumulates `spans` that trac your application as it executes. The OpenInference `Tracer` is a tracer that is specifically designed to work with Phoenix and by default exports the traces to a locally running phoenix server.
 
@@ -199,12 +199,13 @@ import pandas as pd
 # Launch phoenix
 session = px.launch_app()
 
-# Once you have started a Phoenix server, you can start your LangChain application with the OpenInference Tracer as a callback. To do this, you will have to add the tracer to the initialization of your LangChain application:
+# Once you have started a Phoenix server, you can start your LangChain application with the OpenInferenceTracer as a callback. To do this, you will have to instrument your LangChain application with the tracer:
 
-from phoenix.trace.langchain import OpenInferenceTracer
+from phoenix.trace.langchain import OpenInferenceTracer, LangChainInstrumentor
 
 # If no exporter is specified, the tracer will export to the locally running Phoenix server
 tracer = OpenInferenceTracer()
+LangChainInstrumentor(tracer).instrument()
 
 # Initialize your LangChain application
 from langchain.chains import RetrievalQA
@@ -367,13 +368,13 @@ Break-apart your data into clusters of high drift or bad performance using HDBSC
 
 Export your clusters to `parquet` files or dataframes for further analysis and fine-tuning.
 
-## RAG Introspection
+## Retrieval-Augmented Generation Analysis
 
 [![Open in Colab](https://img.shields.io/static/v1?message=Open%20in%20Colab&logo=googlecolab&labelColor=grey&color=blue&logoColor=orange&label=%20)](https://colab.research.google.com/github/Arize-ai/phoenix/blob/main/tutorials/llama_index_search_and_retrieval_tutorial.ipynb) [![Open in GitHub](https://img.shields.io/static/v1?message=Open%20in%20GitHub&logo=github&labelColor=grey&color=blue&logoColor=white&label=%20)](https://github.com/Arize-ai/phoenix/blob/main/tutorials/llama_index_search_and_retrieval_tutorial.ipynb)
 
-![RAG Introspection](https://github.com/Arize-ai/phoenix-assets/blob/main/gifs/corpus_search_and_retrieval.gif?raw=true)
+![RAG Analysis](https://github.com/Arize-ai/phoenix-assets/blob/main/gifs/corpus_search_and_retrieval.gif?raw=true)
 
-Search and retrieval is a critical component of many LLM Applications as it allows you to extend the LLM's capabilities to encompass knowledge about private data. This process is known as RAG (retrieval augmented generation) and often times a vector store is leveraged to store chunks of documents encoded as embeddings so that they can be retrieved at inference time.
+Search and retrieval is a critical component of many LLM Applications as it allows you to extend the LLM's capabilities to encompass knowledge about private data. This process is known as RAG (retrieval-augmented generation) and often times a vector store is leveraged to store chunks of documents encoded as embeddings so that they can be retrieved at inference time.
 
 To help you better understand your RAG application, Phoenix allows you to upload a corpus of your knowledge base along with your LLM application's inferences to help you troubleshoot hard to find bugs with retrieval.
 

{arize_phoenix-0.0.39 → arize_phoenix-0.0.41}/README.md

@@ -28,16 +28,16 @@
 
 Phoenix provides MLOps and LLMOps insights at lightning speed with zero-config observability. Phoenix provides a notebook-first experience for monitoring your models and LLM Applications by providing:
 
--   **LLM App Tracing** - Trace through the execution of your LLM Application to understand the internals of your LLM Application and to troubleshoot problems related to things like retrieval and tool execution.
+-   **LLM Traces** - Trace through the execution of your LLM Application to understand the internals of your LLM Application and to troubleshoot problems related to things like retrieval and tool execution.
 -   **LLM Evals** - Leverage the power of large language models to evaluate your generative model or application's relevance, toxicity, and more.
 -   **Embedding Analysis** - Explore embedding point-clouds and identify clusters of high drift and performance degradation.
--   **RAG Introspection** - Visualize your generative application's search and retrieval process to solve improve your retrieval augmented generation.
+-   **RAG Analysis** - Visualize your generative application's search and retrieval process to solve improve your retrieval-augmented generation.
 -   **Structured Data Analysis** - Statistically analyze your structured data by performing A/B analysis, temporal drift analysis, and more.
 
 **Table of Contents**
 
 -   [Installation](#installation)
--   [LLM App Tracing](#llm-app-tracing)
+-   [LLM Traces](#llm-traces)
     -   [Tracing with LlamaIndex](#tracing-with-llamaindex)
     -   [Tracing with LangChain](#tracing-with-langchain)
 -   [LLM Evals](#llm-evals)
@@ -45,7 +45,7 @@ Phoenix provides MLOps and LLMOps insights at lightning speed with zero-config o
     -   [UMAP-based Exploratory Data Analysis](#umap-based-exploratory-data-analysis)
     -   [Cluster-driven Drift and Performance Analysis](#cluster-driven-drift-and-performance-analysis)
     -   [Exportable Clusters](#exportable-clusters)
--   [RAG Introspection](#rag-introspection)
+-   [Retrieval-Augmented Generation Analysis](#retrieval-augmented-generation-analysis)
 -   [Structured Data Analysis](#structured-data-analysis)
 -   [Community](#community)
 -   [Thanks](#thanks)
@@ -65,7 +65,7 @@ Some functionality such as LLM evals are under the `experimental` subpackage.
 pip install arize-phoenix[experimental]
 ```
 
-## LLM App Tracing
+## LLM Traces
 
 ![LLM Application Tracing](https://github.com/Arize-ai/phoenix-assets/blob/main/gifs/langchain_rag_stuff_documents_chain_10mb.gif?raw=true)
 
@@ -75,7 +75,7 @@ With the advent of powerful LLMs, it is now possible to build LLM Applications t
 
 [![Open in Colab](https://img.shields.io/static/v1?message=Open%20in%20Colab&logo=googlecolab&labelColor=grey&color=blue&logoColor=orange&label=%20)](https://colab.research.google.com/github/Arize-ai/phoenix/blob/main/tutorials/tracing/llama_index_tracing_tutorial.ipynb) [![Open in GitHub](https://img.shields.io/static/v1?message=Open%20in%20GitHub&logo=github&labelColor=grey&color=blue&logoColor=white&label=%20)](https://github.com/Arize-ai/phoenix/blob/main/tutorials/tracing/llama_index_tracing_tutorial.ipynb)
 
-![LLM App Tracing UI](https://storage.googleapis.com/arize-assets/phoenix/assets/images/trace_details_view.png)
+![LLM Traces UI](https://storage.googleapis.com/arize-assets/phoenix/assets/images/trace_details_view.png)
 
 To extract traces from your LlamaIndex application, you will have to add Phoenix's `OpenInferenceTraceCallback` to your LlamaIndex application. A callback (in this case an OpenInference `Tracer`) is a class that automatically accumulates `spans` that trac your application as it executes. The OpenInference `Tracer` is a tracer that is specifically designed to work with Phoenix and by default exports the traces to a locally running phoenix server.
 
@@ -145,12 +145,13 @@ import pandas as pd
 # Launch phoenix
 session = px.launch_app()
 
-# Once you have started a Phoenix server, you can start your LangChain application with the OpenInference Tracer as a callback. To do this, you will have to add the tracer to the initialization of your LangChain application:
+# Once you have started a Phoenix server, you can start your LangChain application with the OpenInferenceTracer as a callback. To do this, you will have to instrument your LangChain application with the tracer:
 
-from phoenix.trace.langchain import OpenInferenceTracer
+from phoenix.trace.langchain import OpenInferenceTracer, LangChainInstrumentor
 
 # If no exporter is specified, the tracer will export to the locally running Phoenix server
 tracer = OpenInferenceTracer()
+LangChainInstrumentor(tracer).instrument()
 
 # Initialize your LangChain application
 from langchain.chains import RetrievalQA
@@ -313,13 +314,13 @@ Break-apart your data into clusters of high drift or bad performance using HDBSC
 
 Export your clusters to `parquet` files or dataframes for further analysis and fine-tuning.
 
-## RAG Introspection
+## Retrieval-Augmented Generation Analysis
 
 [![Open in Colab](https://img.shields.io/static/v1?message=Open%20in%20Colab&logo=googlecolab&labelColor=grey&color=blue&logoColor=orange&label=%20)](https://colab.research.google.com/github/Arize-ai/phoenix/blob/main/tutorials/llama_index_search_and_retrieval_tutorial.ipynb) [![Open in GitHub](https://img.shields.io/static/v1?message=Open%20in%20GitHub&logo=github&labelColor=grey&color=blue&logoColor=white&label=%20)](https://github.com/Arize-ai/phoenix/blob/main/tutorials/llama_index_search_and_retrieval_tutorial.ipynb)
 
-![RAG Introspection](https://github.com/Arize-ai/phoenix-assets/blob/main/gifs/corpus_search_and_retrieval.gif?raw=true)
+![RAG Analysis](https://github.com/Arize-ai/phoenix-assets/blob/main/gifs/corpus_search_and_retrieval.gif?raw=true)
 
-Search and retrieval is a critical component of many LLM Applications as it allows you to extend the LLM's capabilities to encompass knowledge about private data. This process is known as RAG (retrieval augmented generation) and often times a vector store is leveraged to store chunks of documents encoded as embeddings so that they can be retrieved at inference time.
+Search and retrieval is a critical component of many LLM Applications as it allows you to extend the LLM's capabilities to encompass knowledge about private data. This process is known as RAG (retrieval-augmented generation) and often times a vector store is leveraged to store chunks of documents encoded as embeddings so that they can be retrieved at inference time.
 
 To help you better understand your RAG application, Phoenix allows you to upload a corpus of your knowledge base along with your LLM application's inferences to help you troubleshoot hard to find bugs with retrieval.
 

{arize_phoenix-0.0.39 → arize_phoenix-0.0.41}/src/phoenix/__init__.py

@@ -5,7 +5,7 @@ from .session.session import Session, active_session, close_app, launch_app
 from .trace.fixtures import load_example_traces
 from .trace.trace_dataset import TraceDataset
 
-__version__ = "0.0.39"
+__version__ = "0.0.41"
 
 # module level doc-string
 __doc__ = """

{arize_phoenix-0.0.39 → arize_phoenix-0.0.41}/src/phoenix/core/traces.py

@@ -188,7 +188,7 @@ class Traces:
     def token_count_total(self) -> int:
         count = 0
         for span in self._spans.values():
-            count += span[LLM_TOKEN_COUNT_COMPLETION] or 0
+            count += span[LLM_TOKEN_COUNT_TOTAL] or 0
         return count
 
     @property

{arize_phoenix-0.0.39 → arize_phoenix-0.0.41}/src/phoenix/experimental/evals/functions/binary.py

@@ -183,8 +183,16 @@ def _extract_rail(string: str, positive_rail: str, negative_rail: str) -> Option
 
         string = "regular..irregular" - contains both rails
         Output: None
+
+        string = "Irregular"
+        Output: "irregular"
     """
 
+    # Convert the inputs to lowercase for case-insensitive matching
+    string = string.lower()
+    positive_rail = positive_rail.lower()
+    negative_rail = negative_rail.lower()
+
     positive_pos, negative_pos = string.find(positive_rail), string.find(negative_rail)
 
     # If both positive and negative rails are in the string

{arize_phoenix-0.0.39 → arize_phoenix-0.0.41}/src/phoenix/experimental/evals/retrievals.py

@@ -4,7 +4,6 @@ Helper functions for evaluating the retrieval step of retrieval-augmented genera
 
 from typing import List, Optional
 
-from openai import ChatCompletion
 from tenacity import (
     retry,
     stop_after_attempt,
@@ -75,6 +74,9 @@ def classify_relevance(query: str, document: str, model_name: str) -> Optional[b
             (True meaning relevant, False meaning irrelevant), or None if the LLM produces an
             unparseable output.
     """
+
+    from openai import ChatCompletion
+
     prompt = _QUERY_CONTEXT_PROMPT_TEMPLATE.format(
         query=query,
         reference=document,