Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release/v0.27.0 #880

Merged
merged 115 commits into from
Jun 19, 2024
Merged

Release/v0.27.0 #880

merged 115 commits into from
Jun 19, 2024

Conversation

collindutter
Copy link
Member

@collindutter collindutter commented Jun 19, 2024


📚 Documentation preview 📚: https://griptape--880.org.readthedocs.build//880/

collindutter and others added 30 commits March 29, 2024 09:47
Co-authored-by: dylanholmes <4370153+dylanholmes@users.noreply.github.com>
Co-authored-by: Collin Dutter <collin@griptape.ai>
Co-authored-by: Vasily Vasinov <vasily@griptape.ai>
Co-authored-by: Collin Dutter <collin@griptape.ai>
Co-authored-by: Vasily Vasinov <vasily@griptape.ai>
Co-authored-by: Collin Dutter <collin@griptape.ai>
@@ -1,8 +1,8 @@
Griptape provides [Conversation Memory](../griptape-framework/structures/conversation-memory.md) as a means of persisting conversation context across multiple Structure runs.
If you provide it with a suitable Driver, the memory of the previous conversation can be preserved between run of a Structure, giving it additional context for how to respond.
While we can use the [LocalConversationMemoryDriver](../griptape-framework/drivers/conversation-memory-drivers.md#localconversationmemorydriver) to store the conversation history in a local file, this may not be suitable for production use cases.
While we can use the [LocalConversationMemoryDriver](../griptape-framework/drivers/conversation-memory-drivers.md#local) to store the conversation history in a local file, this may not be suitable for production use cases.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Too tantalizing to not tell them WHY it wouldn't be suitable. Disk space?

@@ -1,7 +1,7 @@
In this example we implement a multi-agent Workflow. We have a single "Researcher" Agent that conducts research on a topic, and then fans out to multiple "Writer" Agents to write blog posts based on the research.

By splitting up our workloads across multiple Structures, we can parallelize the work and leverage the strengths of each Agent. The Researcher can focus on gathering data and insights, while the Writers can focus on crafting engaging narratives.
Additionally, this architecture opens us up to using services such as [Griptape Cloud](https://www.griptape.ai/cloud) to have each Agent run on a separate machine, allowing us to scale our Workflow as needed 🤯.
Additionally, this architecture opens us up to using services such as [Griptape Cloud](https://www.griptape.ai/cloud) to have each Agent run on a separate machine, allowing us to scale our Workflow as needed 🤯. To try out how this would work, you can deploy this example as multiple structures from our [Sample Structures](https://github.com/griptape-ai/griptape-sample-structures/tree/main/griptape-multi-agent-workflows) repo.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

run on a separate machine -> run completely independently? Your choice.

@@ -25,3 +25,28 @@ engine.upsert_text_artifacts(

engine.query("what is griptape?", namespace="griptape")
```

## Image
The [Image Query Engine](../../reference/griptape/engines/image_query/image_query_engine.md) is used to execute natural language queries on the contents of images. You can specify the provider and model used to query the image by providing the Engine with a particular [Image Query Driver](../drivers/image-query-drivers.md).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is used to execute -> allows you to perform

@@ -627,7 +627,7 @@ pipeline.run("An image of a mountain shrouded by clouds")

## Image Query Task

The [Image Query Task](../../reference/griptape/tasks/image_query_task.md) executes a natural language query on one or more input images. This Task uses an [Image Query Engine](../engines/image-query-engines.md) configured with an [Image Query Driver](../drivers/image-query-drivers.md) to perform the query. The functionality provided by this Task depend on the capabilities of the model provided by the Driver.
The [Image Query Task](../../reference/griptape/tasks/image_query_task.md) executes a natural language query on one or more input images. This Task uses an [Image Query Engine](../engines/query-engines.md#image) configured with an [Image Query Driver](../drivers/image-query-drivers.md) to perform the query. The functionality provided by this Task depend on the capabilities of the model provided by the Driver.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe I'm just sensitive today, but executes sounds so harsh. perform?

@@ -7,7 +7,8 @@ A [Workflow](../../reference/griptape/structures/workflow.md) is a non-sequentia

Workflows have access to the following [context](../../reference/griptape/structures/workflow.md#griptape.structures.workflow.Workflow.context) variables in addition to the [base context](./tasks.md#context):

* `parent_outputs`: outputs into the current task referenceable by parent task IDs.
* `parent_outputs`: dictionary containing mapping of parent ids to their outputs.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

may I espouse my preference for IDs of ids or Ids

@collindutter collindutter merged commit b0e781c into main Jun 19, 2024
11 checks passed
@collindutter collindutter deleted the release/v0.27.0 branch June 19, 2024 20:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.