Content types received from and sent to a chatbot — Content
Use these functions if you're writing a package that extends ellmer and need
to customise methods for various types of content. For normal use, see
content_image_url() and friends.
ellmer abstracts away differences in the way that different Providers
represent various types of content, allowing you to more easily write
code that works with any chatbot. This set of classes represents types of
content that can be either sent to and received from a provider:
ContentText: simple text (often in markdown format). Text streams yield
only text and thinking content, while content streams can also yield
annotations such as citations and web activity.
ContentCitation: provider-supplied evidence metadata associated with
generated text. Citations are preserved in conversation history but are
not sent back to providers.
ContentImageRemote and ContentImageInline: images, either as a pointer
to a remote URL or included inline in the object. See
content_image_file() and friends for convenient ways to construct these
objects.
ContentToolRequest: a request to perform a tool call (sent by the
assistant).
ContentToolResult: the result of calling the tool (sent by the user).
This object is automatically created from the value returned by calling the
tool() function. Alternatively, expert users can return a
ContentToolResult from a tool() function to include additional data or
to customize the display of the result.
A Shiny Dashboard Template Modular System with Chat Bot Support
A template dashboard system with AI agent integrated. Comes with default themes that can be customized. Developers can upload modified templates on Github, and users can easily download templates with RStudio project wizard. The key features of the default template include light and dark theme switcher, resizing graphs, synchronizing inputs across sessions, new notification system, fancy progress bars, and card-like flip panels with back sides, as well as various of HTML tool widgets.
Inspired by Sweave, the knitr package was designed to be a transparent engine for dynamic report generation with R, and combine features in other add-on packages into one package (knitr ≈ Sweave + …
The knitr package uses a special object to control options and settings (denoted as obj below); it has the following methods:
[…] These objects are visible to users in knitr:
[…] Except …
We can use any languages in knitr, including but not limited to R. Here are some simple demos with Python, Awk, Ruby, Haskell, Bash, Perl, Graphviz, TikZ, SAS, Scala, and CoffeeScript, etc:
[…] …
50 Surprisingly Creative Uses for Vacant Land - Landopia
Discover innovative ways to utilize vacant land, from community gardens to unique events, maximizing its potential for creativity and community engagement.
Deep Dive into FEMA Flood Maps: Gaps, Consequences, and the Role of Innovation
Download issue here Executive Summary FEMA’s flood maps have long been the foundation of how Americans understand and manage flood risk. They shape where communities build, how they insure, and how they prepare. Yet, outdated methodologies and persistent gaps have left millions of homeowners vulnerable, exposing them to significant risks that maps fail to capture. […]
actuarial-data-science/PackageIndividualClaimsSimulator: The IndividualClaimsSimulator may be used for developing and back-testing individual claims reserving methods in non-life insurance
The IndividualClaimsSimulator may be used for developing and back-testing individual claims reserving methods in non-life insurance - actuarial-data-science/PackageIndividualClaimsSimulator
OIDC Authentication and OAuth Authorization for shiny Applications
Provides a simple, configurable framework for OpenID Connect (OIDC) authentication and OAuth 2.0 authorization in shiny applications using S7 classes. Defines providers, clients, and tokens, as well as various supporting functions and a shiny module. Features include cross-site request forgery (CSRF) protection, state encryption, Proof Key for Code Exchange (PKCE) handling, validation of OIDC identity tokens (nonces, signatures, claims), automatic user info retrieval for OIDC and supported OAuth providers, asynchronous flows, and hooks for audit logging.
[show-and-tell] Using {targets} with Docker, DuckDB, and {renv} for Reproducible Data Pipelines · ropensci targets · Discussion #1335
Description I've been working on this project which demonstrates how to build reproducible data pipelines using Docker for isolated environments, DuckDB for fast, in-process SQL analytics, and {tar...