vania-janet/multiturn-rag-retrieval-data huggingface dataset:
curl -X POST --header "Authorization: Bearer {token}" --header "Content-Type: audio/wav" --data-binary @audio1.wav "{url}/v1/acoustic_customizations/{customization_id}/audio/audio1"





 Adding an archive file 

The preferred means of adding audio to a custom acoustic model is to add an archive file that includes multiple audio files. You can add the following types of archive files by specifying the type of the archive with the Content-Type request header:



* A .zip file by specifying application/zip
* A .tar.gz file by specifying application/gzip



You might also need to specify the Contained-Content-Type header depending on the format of the files that you are adding:



* For audio files of type audio/alaw, audio/basic, audio/l16, or audio/mulaw, you must use the Contained-Content-Type header to specify the format of the audio files. Include the rate, channels, and endianness parameters where necessary. In this case, all audio files contained in the archive file must have the same audio format.
* For audio files of all other types, you can omit the Contained-Content-Type header. In this case, the audio files contained in the archive file can have any of the formats not listed in the previous bullet. They do not need to have the same format.



Do not use the Contained-Content-Type header when adding an audio-type resource.

The name of an audio file that is contained in an archive-type resource can include a maximum of 128 characters. This includes the file extension and all elements of the name (for example, slashes).

The following example from [Add audio to the custom acoustic model](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-acousticaddAudio) adds an application/zip file that contains audio files in audio/l16 format that are sampled at 16 kHz:

IBM Cloud
See the following example: (1, "a", "xq"]), (3, "b", "zr"]), (5, "c", "ms"]), (5, "d", "rt"]), (5, "e", "wu"]), (7, "f", "vv"]), (9, "g", "zw"])] || StringSegmentTimeSeries | StringTimeSeries that is segmented. See the following example: (1,(1, "a"), (3, "b")]), (5,(5, "c"), (5, "d"), (5, "e")]), (7,(7, "f"), (9, "g")])] || StringArraySegmentTimeSeries | StringArrayTimeSeries that is segmented. See the following example: (1,(1, "a", "xq"]), (3, "b", "zr"])]), (5,(5, "c", "ms"]), (5, "d", "rt"]), (5, "e", "wu"])]), (7, (7, "f", "vv"]), (9, "g", "zw"])])] ! ! !! !! !! ! ! |<-- </table ""> -->Pseudo data types are not actual data types, but are placeholders that are used by the documentation to represent any of several time series data types.<-- <table> -->Table 2.
: Optional. The type of secret. Choose from tls for certificate CRNs or opaque for non-certificate CRNs. For tls, specify up to one CRN. Foropaque, you can specify multiple CRNs. If no secret type is specified, tls is applied by default.

-q
: Optional: Do not show the message of the day or update reminders.



 Example ingress secret create command 

ibmcloud oc ingress secret create --cert-crn crn:v1:staging:public:cloudcerts:us-south:a/06580c923e40314421d3b6cb40c01c68:0db4351b-0ee1-479d-af37-56a4da9ef30f:certificate:4bc35b7e0badb304e60aef00947ae7ff --cluster my_cluster --type tls --name my_alb_secret --namespace demo_ns







 ibmcloud oc ingress secret field add 

Virtual Private Cloud

Classic infrastructure

Add a non-TLS CRN field to an Opaque secret. There are three ways to specify the field type. The one you choose depends on the secret type and how you want to name the field in the non-TLS secret. For more information, see [Managing non-TLS secret fields](https://cloud.ibm.com/docs/containers?topic=containers-secretsnon-tls-field).

ibmcloud oc ingress secret field add --cluster CLUSTER --name SECRET_NAME --field CRN --namespace NAMESPACE [-q]

Minimum required permissions
: Administrator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

--c, --cluster CLUSTER
: Required. The name or ID of the cluster.

--name NAME
: Required. The name of the secret to add the field to.

--field CRN
: Required. The secret CRN to add to the field.
: Types include Code Engine managed secrets and user managed secrets. If no credentials are needed to access the registry, then the access is None. See [Types of registry access secrets](https://cloud.ibm.com/docs/codeengine?topic=codeengine-add-registrytypes-registryaccesssecrets).

Added information about setting max-scale = 0
: Max scale is the maximum number of instances that can be used for an app. If you set this value to 0, the application scales as needed and is limited only by the resource quota for the project of your app. See [Scaling boundaries](https://cloud.ibm.com/docs/codeengine?topic=codeengine-app-scaleapp-scale-boundaries).

Updated versions for buildpacks
: See [Choosing a build strategy](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-strategy).





 04 March 2022 

Review the release notes for 04 March 2022.

CLI version 1.27.1 released
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).





 02 March 2022 

Review the release notes for 02 March 2022.

CLI version 1.27.0 released
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).

Improved service binding implementation
: CLI 1.27.0 introduces an improved service binding implementation, which is used for all new service bindings. Existing applications and jobs continue to function normally. However, if you want to bind an additional service instance to an app or job, you must first delete any existing service bindings from that app or job. You can then re-create those service bindings with the improved service binding implementation. See [Integrating IBM Cloud services with service binding](https://cloud.ibm.com/docs/codeengine?topic=codeengine-service-binding).
This option is allowed if the --build-type option is git and not allowed if the --build-type option is local. This value is optional.

--image, -i
: The location of the image registry. The format is REGISTRY/NAMESPACE/REPOSITORY:TAG where TAG is optional. If TAG is not specified, the default is latest. This value is optional.

--output, -o
: Specifies the format of the command output. Valid values are json, yaml, jsonpath=JSONPATH_EXPRESSION, and jsonpath-as-json=JSONPATH_EXPRESSION. Use jsonpath to specify the path to an element of the JSON output. This value is optional.

--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.

--registry-secret, --rs
: The registry secret that is used to access the registry. You can add the registry secret by running the registry create command. This value is optional.

--size, --sz
: The size for the build, which determines the amount of resources used. Valid values are small, medium, large, xlarge. For details, see [Determining the size of the build](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-size). This value is optional. The default value is medium.

--source, --src
: The URL of the Git repository that contains your source code; for example https://github.com/IBM/CodeEngine. The source option is required if the --build-type option is git and not allowed if the --build-type option is local. This value is optional.

--strategy, --str
: The strategy to use for building the image. Valid values are dockerfile and buildpacks. This value is optional. The default value is dockerfile.
Select the language of the files that you are adding to this collection.

For information about the languages supported by Discovery, see [Language support](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-language-support).

If you are uploading a PDF document and want to extract party, nature, and category information from it, then expand the Advanced section and click Use the Default Contract Configuration with this collection.



2. Click Next.
3. Click Select documents to upload documents.

Supported file types include PDF, HTML, JSON, Word, Excel, PowerPoint, PNG, TIFF, JPG, GIF, TXT, CSV, ZIP, GZIP, and TAR

No ongoing synchronization of uploaded documents is available. If you want to pick up changes that are made to a document, upload a later version of the document.





2. Wait for the collection to be fully ingested.

Your collection is added to a project that is created for you automatically. The project is a conversational search project with a name like Untitled Project 3; its sole purpose is to store your data collection.
3. Find the project name in the page breadcrumb after your collection is created. Make a note of the project name in case you want to return to the collection from the Discovery application later.
4. 1.5.0 only: If you want to add another collection to the project, click Manage collections, and then click New collection to add another collection.
5. When the project contains all of the data collections that you want to use, click Back to Watson Assistant to finish creating the search skill.
6. Select the project you just created from the list of projects, and then click Configure.





 Data collection creation example 

For example, you might have a JSON file like this one:

{
"Title": "About",
"Shortdesc": "IBM Watson Assistant is a cognitive bot that you can customize for your business needs, and deploy across multiple channels to bring help to your customers where and when they need it.",
"Topics": "overview",
If you would like to include your application-specific binary files, follow the instructions in [Planning for custom images](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) to create your own custom image and use that to build the Slurm cluster through this offering. Note that use of your own custom image might require changes to the cloud-init scripts, and potentially other files, in the Terraform code repository if different post-provisioning actions or variables need to be implemented. String No ibm-ubuntu-20-04-minimal-amd64-2 
 login_node_instance_type Specifies the virtual server instance profile type to be used to create the login node for the Slurm cluster. For choices on profile types, see [Instance profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles). String No bx2-2x8 
 management_node_count Total number of management and management candidate nodes. Enter a value in the range 1 - 3. Number No 1 
 management_node_instance_type Specify the virtual server instance profile type to be used to create the management nodes for the Slurm cluster. For choices on profile types, see [Instance profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles). String No bx2-4x16 
 resource_group Resource group name from your IBM Cloud account where the VPC resources should be deployed. Note: Do not modify the "Default" value if you would like to use the auto scaling capability. For additional information on resource groups, see [Managing resource groups](https://cloud.ibm.com/docs/account?topic=account-rgs). String No Default 
 ssh_allowed_ips Comma-separated list of IP addresses that can access the Slurm instance through an SSH interface. The default value allows any IP address to access the cluster. String No 0.0.0.0/0
[Property type - Secret reference](https://cloud.ibm.com/docs-content/v1/content/f3dada89f147af3b88388a2218ddbf64b3c41e5f/app-configuration/images/ac-property-secret-reference.png)

Figure 6. Property type - Secret reference



1. Specify the Secrets Manager instance information from where the values need to be pulled.



* Resource group: select the resource group from where the Secrets Manager instance to be used.
* Secrets Manager instance: select the Secrets Manager instance to be used for the specified property.



2. Specify the Default value. This value is returned by default and can be overridden while targeting to a segment.



* Secret type: select the secret type from the list. For more information about secret types, see [Working with secrets of different types](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-what-is-secret&interface=uisecret-types).
* Secret name: select the secret name from the dropdown.











 Target collections to properties 

You can add properties to one or more collections either during the creation of property or during editing a property details.

For adding collections to the properties, for the Availability across collections field, select the collection from the list.

If you try to target a property that is not linked to a collection, a window is displayed to add a property to a collection.





 Targeting a segment with properties 

You can roll out property to one or more target segments. You can set different property values for different segments, if needed.



1. From the App Configuration console, go to Properties to display the list of properties available in the current environment of the App Configuration service instance.
2. Click Add targeting in the required property row to display the Target property to segments side panel.

Zoom

!
can't get credentials: Wrong Secret Type.Provided secret of type XXXX.Expected type ibm/ibmc-s3fs The Kubernetes secret that you created for your IBM Cloud Object Storage service instance does not include the type: ibm/ibmc-s3fs. Edit the Kubernetes secret that holds your IBM Cloud Object Storage credentials to add or change the type to ibm/ibmc-s3fs. 
 Bad value for ibm.io/object-store-endpoint XXXX: scheme is missing. Must be of the form http://<hostname> or https://<hostname>Bad value for ibm.io/iam-endpoint XXXX: scheme is missing. Must be of the form http://<hostname> or https://<hostname> The s3fs API or IAM API endpoint has the wrong format, or the s3fs API endpoint could not be retrieved based on your cluster location. See [PVC creation fails due to wrong s3fs API endpoint](https://cloud.ibm.com/docs/containers?topic=containers-cos_api_endpoint_failure). 
 object-path can't be set when auto create is enabled You specified an existing subdirectory in your bucket that you want to mount to your PVC by using the ibm.io/object-path annotation. If you set a subdirectory, you must disable the bucket auto create feature. In your PVC, set ibm.io/auto-create-bucket: "false" and provide the name of the existing bucket in ibm.io/bucket. 
 bucket auto-create must be enabled when bucket auto-delete is enabled In your PVC, you set ibm.io/auto-delete-bucket: true to automatically delete your data, the bucket, and the PV when you remove the PVC. This option requires ibm.io/auto-create-bucket to be set to true, and ibm.io/bucket to be set to "" at the same time.
In this lesson, you will learn how to add documents with linguistic patterns that illustrate the types of rules you want to define.



 About this task 

For more information about adding documents, see [Adding documents for defining rules](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-wks_rule_anno_add).





 Procedure 



1. Download the [documents-new.csv![External link icon](https://cloud.ibm.com/docs-content/v1/content/50eddb8fd81f33092880335ff107a78ff5cd0f65/icons/launch-glyph.svg)](https://watson-developer-cloud.github.io/doc-tutorial-downloads/knowledge-studio/documents-new.csv) file to your computer. This file contains example documents suitable for uploading.
2. Click Rule-based Model > Rules.
3. Click the Add a document icon, which is next to the Documents page heading.
4. Click the Upload CSV file tab.
5. Click to browse for the documents-new.csv file that you downloaded to your computer earlier, and then click Upload.

A set of documents is displayed in the main Documents page.

![Shows three of the fourteen documents that were added to the rule editor. Shows the document title and an excerpt from the beginning of each document. There is also a delete icon next to each document that you can use to delete the document.](https://cloud.ibm.com/docs-content/v1/content/50eddb8fd81f33092880335ff107a78ff5cd0f65/watson-knowledge-studio/images/rule-doc-add3.png)









 Lesson 3: Creating classes 

In this lesson, you will learn how to define classes that you will use when you define a rule.



 About this task
Creating a rule-based model (Experimental) 

This tutorial helps you understand how to create a rule-based model that you can use to find text patterns that you define in documents.

Rule-based models are experimental and are not intended for use in production deployments. Support for the models might be discontinued with short notice.

You will build a model that can find text in documents that matches the pattern month day, year. For example, the model would find the date reference May 1, 2010. Before you define the rule pattern itself, you will create artifacts that will help you build the pattern, including a dictionary class that recognizes month mentions and a regular expression class that recognizes year mentions in text.



 Learning objectives 

After you complete this tutorial, you will know how to perform the following tasks:



* Create classes
* Add documents for defining rules
* Associate dictionaries with classes
* Define regular expressions to capture sequences of characters
* Define rules



This tutorial should take approximately 30 minutes to finish. If you explore other concepts related to this tutorial, it could take longer to complete.





 Before you begin 



* You're using a supported browser. For more information, see [Browser requirements](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-system-requirements).
* You successfully completed [Getting started with Knowledge Studio](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-wks_tutintro), which covers creating a workspace, creating a type system, and adding a dictionary.
* You must have at least one user ID in either the Admin or Project Manager role. For information about user roles, see [User roles in Knowledge Studio](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-roles).







 Results 

After you create the rule-based model, you can use it in one of the following ways to find text patterns in documents:
oc get sc ibmc-vpc-block-10iops-tier -o yaml







 Creating a custom storage class 

Create your own customized storage class with the preferred settings for your Block Storage for Classic instance.

You might create a custom storage class if you want to:



* Set a custom IOPs value.
* Set up Block Storage for VPC with a file system type other than ext4.
* Set up encryption.



To create your own storage class:



1. Review the [Storage class reference](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-blockvpc-block-reference) to determine the profile that you want to use for your storage class. You can also review the [custom profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilescustom) if you want to specify custom IOPs for your Block Storage for VPC.

If you want to use a pre-installed storage class as a template, you can get the details of a storage class by using the oc get sc <storageclass> -o yaml command.
2. Create a customized storage class configuration file.

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: <storage_class_name>
provisioner: vpc.block.csi.ibm.io
parameters:
profile: "<profile>"
csi.storage.k8s.io/fstype: "<file_system_type>"
billingType: "hourly"
encrypted: "<encrypted_true_false>"
encryptionKey: "<encryption_key>"
resourceGroup: ""
zone: "<zone>"
region: "<region>"
tags: "<tags>"
generation: "gc"
classVersion: "1"
iops: "<iops>" Only specify this parameter if you are using a "custom" profile.
allowVolumeExpansion: (true|false) Select true or false.
"type": "map(number)",
"secure": false,
"description":"<description>"
},
{
"name": "<variable_name_x>",
"value": "<variable_value_x>",
"type": "tuple(string, list(string), number, bool])",
"secure": false,
"description":"<description>"
},
{
"name": "<variable_name_x>",
"value": "<variable_value_x>",
"type": "any",
"secure": false,
"description":"<description>"
}
]
}
]
}
Show more



JSON file component description

 Parameter Required / Optional Description 

 workspace_name Optional Enter a name for your workspace. For more information, see [Designing your workspace structure](https://cloud.ibm.com/docs/schematics?topic=schematics-workspace-setupstructure-workspace). 
 terraform_version Optional The Terraform version that you want to use to run your Terraform code. Enter terraform_v1.1 to use Terraform version 1.1,terraform_v1.0 to use Terraform version 1.0, and similarly, terraform_v0.15, terraform_v0.14, terraform_v0.13, terraform_v0.12. For example, when you specify terraform_v1.1 means users can have template that are of Terraform v1.1.0, v1.1.1, or v1.1.2, so on. Make sure that your Terraform config files are compatible with the Terraform version that you specify. This is a required variable. If the Terraform version is not specified, By default, Schematics selects the version from your template.
Select Start creating.
3. Select a project from the list of available projects. You can also [create a new one](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-projectcreate-a-project). Note that you must have a selected project to create a function.
4. Select Function.
5. Enter a name for the function. Use a name for your function that is unique within the project.
6. Select Node.js 18
7. Click Create. Your function is created with sample code. You can edit this code on the Function -> Configuration page.
8. Click Test function and then click Send request in the Test function pane. To open the function in a web page, click Function URL.



Example output

{"args":{"__ce_headers":{"Accept-Encoding":"gzip, deflate, br","User-Agent":"got (https://github.com/sindresorhus/got)","X-Request-Id":"12340a7b-11c0-4de3-f16b-a6abc27f4146"},"__ce_method":"GET","__ce_path":"/"},"env":{"HOME":"/root","PATH":"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/lib/nodejs/bin","PWD":"/nodejsAction","SHLVL":"1","_":"/usr/local/lib/nodejs/bin/node","__OW_ALLOW_CONCURRENT":"true","container":"oci"}}

You deployed your first function to Code Engine and tested it out.
<xsd:annotation>
<xsd:documentation>
<para>Full data type. e,g, VARCHAR(20).</para>
<para>ARRAY</para>
<para>BIGINT</para>
<para>BINARY</para>
<para>BIT</para>
<para>BLOB</para>
<para>BOOLEAN</para>
<para>CHAR precision is used as length: CHAR(N)</para>
<para>CLOB</para>
<para>DATALINK</para>
<para>DATE</para>
<para>DECIMAL precision and scale are used: DECIMAL(N, M)</para>
<para>DISTINCT user defined type</para>
<para>DOUBLE</para>
<para>FLOAT</para>
<para>INTEGER</para>
<para>JAVA_OBJECT</para>
<para>LONGNVARCHAR see CHAR</para>
<para>LONGVARBINARY see CHAR</para>
<para>LONGVARCHAR see CHAR</para>
<para>NCHAR see CHAR</para>
<para>NCLOB</para>
<para>NULL</para>
<para>NUMERIC see DECIMAL</para>
<para>NVARCHAR see CHAR</para>
<para>OTHER</para>
<para>REAL</para>
<para>REF</para>
<para>ROWID</para>
<para>SMALLINT</para>
<para>SQLXML</para>
<para>STRUCT</para>
<para>TIME</para>
<para>TIMESTAMP</para>
<para>TINYINT</para>
<para>VARBINARY see CHAR</para>
<para>VARCHAR see CHAR</para>
<para>TIMESTAMP_TZ</para>
<para>TIME_TZ</para>