Chris B. France cbfrance

## predefined-responses-framework.md

      
              1 file
            
          
              0 forks
            
          
              2 comments
            
          
              1 star
            
          
                lost-books
                / predefined-responses-framework.md
            
            
              Created
              April 8, 2023 17:46
            
              
                Predefined Responses For LLMs Framework Sketch 
              
          
    A common framework for required elements that companies offering LLMs should provide as predefined, verified responses could be established as a set of best practices. These best practices would aim to enhance transparency, ensure ethical conduct, and provide users with accurate and important information about the LLM. Here are some potential common requirements and best practices for predefined, verified responses:


Model Identification: Chatbots should clearly and accurately identify the LLM or AI technology used, including the name, version, and source (proprietary or open-source).


Model Capabilities and Limitations: Chatbots should provide information about the capabilities, strengths, and limitations of the LLM, including any known biases or potential inaccuracies.


Model Card and Documentation: Chatbots should link to model cards or official documentation that describe the LLM's abilities, limitations, training data, evaluation metrics, risks, and ethical considerations.


**Use Case


## build.js
var fs = require("fs");
var path = require("path");

// Config params (relative to where npm/script is called from):
const APP_BASE = './src';
const ENTRY_FILE = `index.tsx`;
const OUTPUT_DIR = './build';
const OUTPUT_FILE = 'app.js';
const IS_DEV = false;
const TARGET = 'es2018';

## d3-in-react.js
import React, { useRef, useEffect } from 'react';
import * as d3 from 'd3';

interface IProps {
    data?: number[];
}

/* Component */
export const MyD3Component = (props: IProps) => {
    /* The useRef Hook creates a variable that "holds on" to a value across rendering

## myscript.sh
#! /bin/bash

# ECHO COMMAND
# echo Hello World!

# VARIABLES
# Uppercase by convention
# Letters, numbers, underscores
NAME="Bob"
# echo "My name is $NAME"

## conditionalwrap.js
import React from 'react';

const ConditionalWrap = ({condition, wrap, children}) => condition ? wrap(children) : children;

const Header = ({shouldLinkToHome}) => (
  <div>
    <ConditionalWrap
      condition={shouldLinkToHome}
      wrap={children => <a href="/">{children}</a>}
    >

## hubot-wizard.coffee
#
# Description:
#     Have a multi-step conversation with hubot
#
# Commands:
#     hubot start wizard - Allow hubot to ask you some questions
#

module.exports = (robot) ->

## HOTQuickstart.md

      
              1 file
            
          
              7 forks
            
          
              4 comments
            
          
              23 stars
            
          
                meetar
                / HOTQuickstart.md
            
            
              Last active
              July 30, 2020 12:15
            
              
                How to get started contributing to a Humanitarian OpenStreetMap task
              
          
    ##How to get started contributing to a Humanitarian OpenStreetMap Team task
###Overview
OpenStreetMap (OSM) is an open-source map of the world that anyone can edit. But like any map, it's incomplete.
The Humanitarian OpenStreetMap Team (HOT) helps organize people to improve the OSM map for crisis areas, mostly so aid workers can find their way around and make decisions about undermapped places. The data in these crisis areas is often very poor, or completely non-existent. Therefore any contribution you make at all will be a vast improvement, and could materially help people who are on the ground right now, looking at this data as you edit it, and deciding where to go and who to help.
There are many HOT tasks active at once. As of August 2014, the highest-priority tasks are Gaza and areas affected by the West African Ebola outbreak.

  
## make_favicon.sh
# IE is still braindead so still use favicon.ico

convert -resize x16 -gravity center -crop 16x16+0+0 -flatten -colors 256 input.png output-16x16.ico
convert -resize x32 -gravity center -crop 32x32+0+0 -flatten -colors 256 input.png output-32x32.ico
convert output-16x16.ico output-32x32.ico favicon.ico

# Then, HTML needs to specify size="XxY" as largest size due to browser bugs

<link rel="shortcut icon" href="/favicon.ico" sizes="32x32">

## apple.html
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns:d="http://www.apple.com/DTDs/DictionaryService-1.0.rng">
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
  </head>
  <body>
    <d:entry id="m_en_gb0035330" d:title="apple" class="entry">
      <span class="hg">
        <span d:dhw="1" role="text" linebreaks="apple" class="hw">apple</span>

## Variables.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>SKVariables</key>
	<array>
		<dict>
			<key>enabled</key>
			<true/>
			<key>name</key>
	var fs = require("fs");
	var path = require("path");

	// Config params (relative to where npm/script is called from):
	const APP_BASE = './src';
	const ENTRY_FILE = `index.tsx`;
	const OUTPUT_DIR = './build';
	const OUTPUT_FILE = 'app.js';
	const IS_DEV = false;
	const TARGET = 'es2018';
	import React, { useRef, useEffect } from 'react';
	import * as d3 from 'd3';

	interface IProps {
	data?: number[];
	}

	/* Component */
	export const MyD3Component = (props: IProps) => {
	/* The useRef Hook creates a variable that "holds on" to a value across rendering
	#! /bin/bash

	# ECHO COMMAND
	# echo Hello World!

	# VARIABLES
	# Uppercase by convention
	# Letters, numbers, underscores
	NAME="Bob"
	# echo "My name is $NAME"
	import React from 'react';

	const ConditionalWrap = ({condition, wrap, children}) => condition ? wrap(children) : children;

	const Header = ({shouldLinkToHome}) => (
	<div>
	<ConditionalWrap
	condition={shouldLinkToHome}
	wrap={children => <a href="/">{children}</a>}
	>
	#
	# Description:
	# Have a multi-step conversation with hubot
	#
	# Commands:
	# hubot start wizard - Allow hubot to ask you some questions
	#

	module.exports = (robot) ->
	# IE is still braindead so still use favicon.ico

	convert -resize x16 -gravity center -crop 16x16+0+0 -flatten -colors 256 input.png output-16x16.ico
	convert -resize x32 -gravity center -crop 32x32+0+0 -flatten -colors 256 input.png output-32x32.ico
	convert output-16x16.ico output-32x32.ico favicon.ico

	# Then, HTML needs to specify size="XxY" as largest size due to browser bugs

	<link rel="shortcut icon" href="/favicon.ico" sizes="32x32">
	<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
	<html xmlns:d="http://www.apple.com/DTDs/DictionaryService-1.0.rng">
	<head>
	<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
	</head>
	<body>
	<d:entry id="m_en_gb0035330" d:title="apple" class="entry">
	<span class="hg">
	<span d:dhw="1" role="text" linebreaks="apple" class="hw">apple</span>
	<?xml version="1.0" encoding="UTF-8"?>
	<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
	<plist version="1.0">
	<dict>
	<key>SKVariables</key>
	<array>
	<dict>
	<key>enabled</key>
	<true/>
	<key>name</key>