Skip to content

Commit 9e644fb

Browse files
authored
Vignette and readme edits (#33)
* reread * update readme * render readme
1 parent 600433b commit 9e644fb

7 files changed

Lines changed: 217 additions & 256 deletions

File tree

.gitignore

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,6 @@ scratch*
33
inst/doc
44
*ragnar.duckdb
55
docs
6+
.claude
67
_chats/
78
*chat.Rmd
8-
.claude

README.Rmd

Lines changed: 17 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,9 @@
11
---
22
output: github_document
3+
editor:
4+
markdown:
5+
canonical: true
6+
wrap: 72
37
---
48

59
<!-- README.md is generated from README.Rmd. Please edit that file -->
@@ -11,6 +15,7 @@ knitr::opts_chunk$set(
1115
fig.path = "man/figures/README-",
1216
out.width = "100%"
1317
)
18+
unlink("r4ds.ragnar.duckdb")
1419
```
1520

1621
# ragnar <img src="man/figures/logo.png" align="right" height="138"/>
@@ -26,7 +31,7 @@ Generation (RAG) workflows. It focuses on providing a complete solution
2631
with sensible defaults, while still giving the knowledgeable user
2732
precise control over each steps. We don't believe that you can fully
2833
automate the creation of a good RAG system, so it's important that
29-
`ragnar` is not a black box. `ragnar` is designed to be transparent—you
34+
`ragnar` is not a black box. `ragnar` is designed to be transparent. You
3035
can inspect easily outputs at intermediate steps to understand what's
3136
happening.
3237

@@ -46,14 +51,15 @@ to Markdown.
4651

4752
Key functions:
4853

54+
- `ragnar_read()`: Convert a file or URL to a dataframe
55+
- `read_as_markdown`: Convert a file or URL to markdown
4956
- `ragnar_find_links()`: Find all links in a webpage
50-
- `ragnar_read()`: Convert a file or URL to markdown
5157

5258
### 2. Text Chunking
5359

54-
Next we divide each document into multiple chunks. Ragnar defaults to a
55-
strategy that preserves some of the semantics of the document, but
56-
provide plenty of options to tweak the approach.
60+
Next we divide each document into chunks. Ragnar defaults to a strategy
61+
that preserves some of the semantics of the document, but provide plenty
62+
of opportunities to tweak the approach.
5763

5864
Key functions:
5965

@@ -67,10 +73,10 @@ Key functions:
6773
### 3. Context Augmentation (Optional)
6874

6975
RAG applications benefit from augmenting text chunks with additional
70-
context, such as document headings and subheadings. While `ragnar`
71-
doesn't directly export functions for this, it supports template-based
72-
augmentation through `ragnar_read(frame_by_tags, split_by_tags)`. Future
73-
versions will support generating context summaries via LLM calls.
76+
context, such as document headings and subheadings. `ragnar` makes it
77+
easy to keep track of headings and subheadings as part of chunking,
78+
which can then be used to support template-based augmentation. (See
79+
examples below)
7480

7581
Key functions:
7682

@@ -84,7 +90,7 @@ Key functions:
8490

8591
`ragnar` can help compute embeddings for each chunk. The goal is for
8692
`ragnar` to provide access to embeddings from popular LLM providers.
87-
Currently only `ollama` and `openai` providers.
93+
Currently `ollama` and `openai` providers are supported.
8894

8995
Key functions:
9096

@@ -122,11 +128,7 @@ Key functions:
122128
- `ragnar_retrieve_bm25()`: Retrieve using
123129
[`full-text search DuckDB extension`](https://duckdb.org/docs/extensions/full_text_search.html)
124130

125-
### 7. Re-ranking (Optional)
126-
127-
Re-ranking of retrieved chunks is planned for future releases.
128-
129-
### 8. Prompt Generation
131+
### 7. Chat Augmentation
130132

131133
`ragnar` can equip an `ellmer::Chat` object with a retrieve tool that
132134
enables an LLM to retreive content from a store on-demand.

0 commit comments

Comments
 (0)