vania-janet/multiturn-rag-retrieval-data huggingface dataset:
-0.0196278877556324,-0.00027448884793557227],-0.0197282787412405,-0.00027589278761297464],-0.019823499023914337,-0.00027722440427169204],-0.019913479685783386,-0.0002784827374853194],-0.019998157396912575,-0.00027966691413894296],-0.02007746882736683,-0.0002807760611176491],-0.020151358097791672,-0.00028180936351418495],-0.020219773054122925,-0.0002827661228366196],-0.02028266154229641,-0.00028364561148919165],-0.020339980721473694,-0.000284447189187631],-0.020391687750816345,-
[The "Add a class" icon](images/wks_tut_dict_add.jpg "The "Add a class" icon") next to Class from the right side panel.
2. Enter RegExpYear as the class name, and click Add.
3. Click the Regex tab, and then click the Create a regular expression icon next to the Regular Expressions heading.
4. Click Add Entry.
5. In the Regular Expression field, enter the following expression, which finds years between 1900 and 2099:

(?:(?:19|20)[0-9]{2})
6. Set Minimum Word Tokens to 1 and Maximum Word Tokens to 1.
7. Click Add to save the regular expression entry.
8. Enter MyYearExp as the regular expression name, and then, from the Class menu, select the RegExpYear class that you defined earlier.
9. Click Save.

After you save the regular expression, it is automatically applied to the sample documents. Any text strings that follow the pattern that you defined in the regular expression are annotated as mentions of the RegExpYear class.
10. To check whether the expression you defined is capturing time occurrences correctly, you can search for mentions. Click the Search annotations in documents icon next to the RegExpYear class in the Class panel.

![Shows the hovering over the magnifying glass icon next to the "RegExpYear" class in the Class panel of the Rules page.](images/rule-regex-add5.png "Shows the cursor hovering over the magnifying glass icon next to the "RegExpYear" class in the Class panel of the Rules page.")

The Find Annotations page is displayed. Occurrences of year mentions are highlighted in the sample documents in which they occur.

![Shows eight annotations of years highlighted in excerpts from the sample documents.]
"subtypes":null,
"roles":["b9d6caa2-90ac-47ff-91f6-2149b8ffcf20","93ba1f27-173f-4714-b31e-77bdd8cb9932"],
"clazz":null,
"and so on"
}
},
{
"id":"b9d6caa2-90ac-47ff-91f6-2149b8ffcf20",
"label":"FURNITURE_PATIO",
"sireProp":{
"mentionType":null,
"subtypes":null,
"roles":["b9d6caa2-90ac-47ff-91f6-2149b8ffcf20","93ba1f27-173f-4714-b31e-77bdd8cb9932"],
"clazz":null,
"and so on"
}
},
{
"id":"b9d6caa2-90ac-47ff-91f6-2149b8ffcf20",
"label":"FURNITURE_LIVING",
"sireProp":{
"mentionType":null,
"subtypes":null,
"roles":["b9d6caa2-90ac-47ff-91f6-2149b8ffcf20","93ba1f27-173f-4714-b31e-77bdd8cb9932"],
"clazz":null,
"and so on"
}
},
{
"id":"b9d6caa2-90ac-47ff-91f6-2149b8ffcf20",
"label":"FURNITURE_DINING",
"sireProp":{
"mentionType":null,
"subtypes":null,
"_revisions":{"start":1,"ids":"2c5ee70689bb75af6f65b0335d1c92f4"]}},
{"_id":"doc4","_rev":"1-0923b723c62fe5c15531e0c33e015148",
"firstname":"Anna","lastname":"Greene","age":44,
"location":"Baton Rouge, LA",
"_revisions":{"start":1,"ids":"0923b723c62fe5c15531e0c33e015148"]}},
{"_id":"doc1","_rev":"1-cce7796c7113c5498b07d8e11d7e0c12",
"firstname":"Sally","lastname":"Brown","age":16,
"location":"New York City, NY",
"_revisions":{"start":1,"ids":"cce7796c7113c5498b07d8e11d7e0c12"]}},
{"_id":"doc5","_rev":"1-19f7ecbc68090bc7b3aa4e289e363576",
"firstname":"Lois","lastname":"Brown","age":33,
"location":"Syracuse, NY",
"_revisions":{"start":1,"ids":"19f7ecbc68090bc7b3aa4e289e363576"]}},
{"_id":"doc3","_rev":"1-f6055e3e09f215c522d45189208a1bdf",
[classify](https://cloud.ibm.com/apidocs/natural-language-classifierclassify-a-phrase) Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, classifier_id, text, Classify a phrase. 
 [classify-collection](https://cloud.ibm.com/apidocs/natural-language-classifierclassify-multiple-phrases) Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, classifier_id, collection Classify multiple phrases. 
 [create-classifier](https://cloud.ibm.com/apidocs/natural-language-classifiercreate-classifier) Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, metadata, training_data Create a classifier. 
 [delete-classifier](https://cloud.ibm.com/apidocs/natural-language-classifierdelete-classifier) Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, classifier_id Delete a classifier. 
 [get-classifier](https://cloud.ibm.com/apidocs/natural-language-classifierget-information-about-a-classifier) Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, classifier_id Get information about a classifier.
{"entity":"sys-date","location":6,9],"value":"2017-08-07",
"confidence":1,"metadata":{"calendar_type":"GREGORIAN",
"timezone":"America/New_York"}},
{"entity":"sys-time","location":6,9],"value":"15:01:00",
"confidence":1,"metadata":{"calendar_type":"GREGORIAN",
"timezone":"America/New_York"}}
]



 When placement of entities in the input matters 

When you use the shorthand expression, @city.contains('Boston'), in a condition, the dialog node returns true only ifBoston is the first entity detected in the user input. Only use this syntax if the placement of entities in the input matters to you and you want to check the first mention only.

Use the full SpEL expression if you want the condition to return true any time the term is mentioned in the user input, regardless of the order in which the entities are mentioned. The condition, entities['city']?.contains('Boston') returns true when at least one 'Boston' city entity is found in all the @city entities, regardless of placement.

For example, a user submits "I want to go from Toronto to Boston." The @city:Toronto and @city:Boston entities are detected and are represented in the array that is returned as follows:



* entities.city[0].value = 'Toronto'
* entities.city[1].value = 'Boston'



The order of entities in the array that is returned matches the order in which they are mentioned in the user input.





 Entity properties 

Each entity has a set of properties associated with it. You can access information about an entity through its properties.



 Property Definition Usage tips 

 confidence A decimal percentage that represents your assistant's confidence in the recognized entity. The confidence of an entity is either 0 or 1, unless you have activated fuzzy matching of entities. When fuzzy matching is enabled, the default confidence level threshold is 0.3.
This pattern can be explained as “match either one A.match OR a sequence of a B.match followed by a C.match. You can see a complete example that uses the | operator in Example 1.

After you created your pattern, each match to your <pattern specification> constructs an output result according to the return clause of the pattern specification, as well as the optional <select list> at the beginning of the extract statement. The results are filtered and consolidated according to the having, consolidate, and limit clauses of the extract statement. For example, if multiple overlapping matches exist for the pattern specification, all of the possible matches are returned, and you can use a consolidation clause to filter out redundant outputs.

Consider the previous example, but now the goal is to remove matches that contain the word 'Sheraton', and to consolidate resulting matches by removing the ones that are contained within a larger match. For example, we do not want to find “Best Garden Hotel” and also “Garden Hotel” across the same span of text.

create view HotelCandidate as
extract
pattern <CW.word>{1,3} /[Hh]otel/ as hotelname
from CapsWord CW
having Not(ContainsRegex(/.Sheraton./,hotelname))
consolidate on hotelname using 'ContainedWithin';



Now that you are familiar with the syntax and some examples, this diagram outlines the full syntax for the pattern specification. Refer to this full syntax when you start building patterns to see how to structure the pattern that you want to build.

If you are familiar with POSIX character-based regular expressions, then you recognize that the syntax is similar. In this case, the syntax allows for white space between elements, and what an element can be in order to suit the AQL purposes is also defined.Note that the term Alternation in this case means choice. Using a vertical bar between elements indicates that a choice exists, which can be grouped by using ( ) .

Pattern -> Alternation
Alternation -> Sequence | Sequence | ... | Sequence
Sequence -> Optional Optional ... Optional
Optional -> Repeat | Repeat ? Repeat -> Atom | Atom { min, max }
To display the array as text, use the join method in the expression like this:

The available flights are <? $flights.joinToArray("%e.flight%").join(", "). ?>

The response is, The available flights are DL1040, DL1710, DL4379.



 Complex template 

To create a more complex template, instead of specifying the template details in the method parameter directly, you can create a context variable.

This template context variable contains a subset of the array elements and adds labels in front of them, so the information will be displayed in a legible list in the response:

"template": "<br/>Flight number: %e.flight% <br/> Airline: %e.carrier% <br/> Departure date: %e.departure_date% <br/> Departure time: %e.departure_time% <br/> Arrival time: %e.arrival_time% <br/>"

Use this expression in the dialog node response to apply the template defined in $template to the array in $flights.

The flight info is <? $flights.joinToArray($template).join(" ") ?>

The response looks like this:

The flight info is
Flight number: DL1040
Airline: Alitalia
Departure date: 2019-02-02
Departure time: 16:45
Arrival time: 07:00

Flight number: DL1710
Airline: Delta
Departure date: 2019-02-02
Departure time: 07:00
Arrival time: 10:19

Flight number: DL4379
Airline: Virgin Atlantic
Departure date: 2019-02-02
Departure time: 21:40
Arrival time: 09:05

The advantage of using this method is that it doesn't matter how often the values in the array change or whether the number of elements in the array increases. As long as each array element contains at least the subset of properties that are referenced by the template, then the expression works.





 JSON Object template example
* ibmcloud is backup-policy-jobs bkp-policy-do-not-delete --snapshots crn:v1:staging:public:is:us-south:a/efe5afc483594adaa8325e2b4d1290df::snapshot:r134-c4ea5585-0554-40db-bdc8-1ec9fb15098b,crn:v1:staging:public:is:us-south:a/efe5afc483594adaa8325e2b4d1290df::snapshot:r134-c10755ee-db71-472e-bf80-01e21229fda0
* ibmcloud is backup-policy-jobs bkp-policy-do-not-delete --snapshots-crns crn:v1:staging:public:is:us-south:a/efe5afc483594adaa8325e2b4d1290df::snapshot:r134-c4ea5585-0554-40db-bdc8-1ec9fb15098b,crn:v1:staging:public:is:us-south:a/efe5afc483594adaa8325e2b4d1290df::snapshot:r134-c10755ee-db71-472e-bf80-01e21229fda0
* ibmcloud is backup-policy-jobs bkp-policy-do-not-delete --source r134-71757aee-5e90-40f5-bd7d-0a538c084efb







 Command options 



* POLICY: ID or name of the backup policy.
* --source: ID or name of the source volume. Source name can be used only if the source exists inside the VPC.
* --snapshots: IDs, names, or CRNs of target snapshots. Combinations of these three types are not supported. Passing is supported by only one of these three types.
: For classic clusters in Dallas and Frankfurt, updated the required IP addresses and ports that you must open in a [public gateway firewall device](https://cloud.ibm.com/docs/openshift?topic=openshift-firewallfirewall_outbound), [private gateway device firewall](https://cloud.ibm.com/docs/openshift?topic=openshift-firewallfirewall_private), or [Calico network isolation policies](https://github.com/IBM-Cloud/kube-samples/tree/master/calico-policies).





 2 November 2020 

Persistent storage
: Added the following topics.



* [Creating IBM Cloud Object Storage service credentials](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-cos-understandcreate_cos_secret)
* [Adding your IBM Cloud Object Storage credentials to the default storage classes](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-cos-understandservice_credentials)
* [Backing up and restoring storage data](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_br)



Version 4 Ingress
: Added a troubleshooting topic for [VPC load balancer health status failures](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc_lb_healthcheck) in version 4 VPC clusters.







 October 2020 



 26 October 2020 

Master versions
: Master fix pack update change log documentation is available.
For more information on the options available for your snapshot schedule, refer to the [CLI documentation](https://cloud.ibm.com/docs/cli?topic=cli-sl-block-storagesl_block_snapshot_enable).

ibmcloud sl block snapshot-enable VOLUME_ID <OPTIONS>
10. To restore data from a snapshot to an existing volume, run the following command.

ibmcloud sl file snapshot-restore <volume_ID> <snapshot_ID>







 Replicating snapshots to another zone 

To protect your data from a zone failure, you can [replicate snapshots](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-replicationreplication) to a File Storage for Classic instance that is set up in another zone.

Data can be replicated from the primary storage to the backup storage only. You can't mount a replicated File Storage for Classic instance to a cluster. When your primary storage fails, you can manually set your replicated backup storage to be the primary one. Then, you can mount it to your cluster. After your primary storage is restored, you can restore the data from the backup storage.





 Duplicating storage 

You can [duplicate your File Storage for Classic instance](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-duplicatevolumeduplicatevolume) in the same zone as the original storage instance.

A duplicate has the same data as the original storage instance at the point in time that you create the duplicate. Unlike replicas, use the duplicate as an independent storage instance from the original. To duplicate, first [set up snapshots for the volume](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-snapshots).





 Backing up data to IBM Cloud® Object Storage 

You can use the [ibm-backup-restore Helm chart](https://cloud.ibm.com/docs/openshift?topic=openshift-utilitiesibmcloud-backup-restore) to spin up a backup and restore pod in your cluster.
To associate backup policies, you can add a backup policy's tags for target resources to this volume. Click Apply to select a backup policy, then apply its tags for the target resource to the volume. 



Table 4 shows Actions menu options from the volume details page.



Table 4. Actions menu options one the volume details page.

 Action Description 

 Create snapshot Create a snapshot from a data volume or a "bootable snapshot" from a boot volume. Data volumes must be attached to a virtual server instance. For more information, see [Create a snapshot in the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-create&interface=uisnapshots-vpc-create-ui). 
 Create image Create an image from the boot volume. For more information, see [Create an image from the list of boot volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-create-ifvimport-custom-image-vol). 
 Expand volume [Increase the size](https://cloud.ibm.com/docs/vpc?topic=vpc-expand-block-storage-vol-concepts) of a data volume in GBs. 
 Edit IOPS profile For data volumes that are attached to a virtual server instance, increase or decrease IOPS by [editing the IOPS profile](https://cloud.ibm.com/docs/vpc?topic=vpc-adjusting-volume-iops). 
 Delete [Delete](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storagedelete) the volume. You must first detach the volume from an instance before you attempt to delete it. 







 Viewing attached Block Storage for VPC volume details in instance details 

You can view information about an attached Block Storage for VPC volume from the Virtual server instance details page:



1. In the [IBM Cloud console)](https://cloud.ibm.com/login), go to the menu !
* ibmcloud is snapshots --source-image ibm-centos-7-9-minimal-amd64-9
* ibmcloud is snapshots --source-image crn:v1:staging:public:is:us-east:a/efe5afc483594adaa8325e2b4d1290df::image:r134-24d856e2-6aec-41c2-8f36-5a8a3766f0d6
* ibmcloud is snapshots --backup-policy-plan r134-7d36a9df-9512-496e-8ad0-054cb4dd854c --backup-policy r134-3f56e0fa-1cfb-4341-9e57-de2a6345e7b3
* ibmcloud is snapshots --backup-policy-plan bkp-plan-do-not-delete --backup-policy bkp-policy-do-not-delete







 Command options 



* --volume: ID, name, or CRN of the source volume.
* --tag: Tag for this resource.
* --source-image: ID, name, or CRN of the source image.
* --backup-policy-plan: ID or name of the backup policy plan.
* --backup-policy: ID or Name of the backup policy.
* --clones-zone-name: Name of the snapshot clone zone.
* --resource-group-id: ID of the resource group. This ID is mutually exclusive with --resource-group-name.
* --resource-group-name: Name of the resource group. This name is mutually exclusive with --resource-group-id.
* --all-resource-groups: Query all resource groups.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------
Contact your IBM Sales representative if you are interested in getting access.



Table 24. Actions that generate events for file storage resources

 Resource Action Description 

 shares is.share.share.create File share was created 
 shares is.share.share.read One or more file shares were retrieved 
 shares is.share.share.update File share was updated 
 shares is.share.share.delete File share was deleted 
 shares is.share.share.split Replication relationship is removed between two file shares 
 shares is.share.share.failover Replication relationship is reversed between two file shares 
 shares is.share.share.schedule.modification The replication schedule was modified. 
 share mount targets is.share.mount-target.create Mount target for a file share was created 
 share mount targets is.share.mount-target.read One mount target for a file share was retrieved 
 share mount targets is.share.mount-target.list List of all mount targets for a file share was retrieved 
 share mount targets is.share.mount-target.update Mount target for a file share was modified 
 share mount targets is.share.mount-target.delete Mount target for a file share was deleted 







 Backup service events 

The following table lists the actions that are related to the VPC Backup service resources and the generation of events.



Table 25. Actions that generate events for VPC Backup service resources

 Resource Action Description 

 backup-policy is.backup-policy.backup-policy.create Backup policy was created 
 backup-policy is.backup-policy.backup-policy.update Backup policy was updated 
 backup-policy is.backup-policy.backup-policy.delete Backup policy was deleted 
 backup-policy is.backup-policy.backup-policy.list One or more backup policies were retrieved 
 backup-policy is.backup-policy.backup-policy.read Backup policy was retrieved 
 backup-policy is.backup-policy.backup-plan.create Backup plan was created 
 backup-policy is.backup-policy.backup-plan.delete Backup plan was deleted 
 backup-policy is.backup-policy.backup-plan.read One or more backup plans were retrieved 
 backup-policy is.backup-policy.backup-job.read One or more backup jobs were retrieved 









 Supported locations
: Version 2.1.16 of the IBM Cloud Object Storage plug-in [is available](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_plugin_changelog).

Block Storage for VPC add-on.
: [Version 4.3.0_1163](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc_bs_changelog) is available.

Block Storage for VPC add-on.
: [Version 4.2.6_1161](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc_bs_changelog) is available.





 20 May 2022 

Worker node fix pack
: Red Hat OpenShift [4.10.14_1519_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_410),[4.9.33_1539_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_49), [4.8.39_1557_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_48), [4.7.50_1564_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_47), [4.6.57_1583_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_46), [3.11.685_1632_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311).

IBM Cloud Container Registry private IP address changes beginning 23 June 2022
* [Preserving the source IP address](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationspreserve_source_ip)



* [Enabling the PROXY protocol in VPC clusters](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationspreserve_source_ip_vpc)
* [Changing the externalTrafficPolicy in classic clusters](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationspreserve_source_ip_classic)



* [Configuring SSL protocols and SSL ciphers at the HTTP level](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationsssl_protocols_ciphers)
* [Sending your custom certificate to legacy clients](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationsdefault_server_cert)
* [Tuning ALB performance](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationsperf_tuning)



* [Enabling log buffering and flush timeout](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationsaccess-log)
* [Changing the number or duration of keepalive connections](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationskeepalive_time)
* [Changing the number of simultaneous connections or worker processes](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationsworker_processes_connections)
* [Changing the number of open files for worker processes](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationsmax-worker-files)
* ibmcloud is backup-policy-jobs bkp-policy-do-not-delete --snapshots r134-f1d9b974-14e5-4a2e-8e38-c023164be316,r134-b11f1540-288d-4331-97ab-f565ca15a3b8,r134-ab3147a3-715f-4017-8fed-ea3ddadeeb1d,r134-435b8414-dae2-4026-847f-a73162105e5f
* ibmcloud is backup-policy-jobs bkp-policy-do-not-delete --snapshots bkp-plan-do-not-delete-31addff28e2b-422b,bkp-plan-do-not-delete-f37bc1f19123-4995
* ibmcloud is backup-policy-jobs bkp-policy-do-not-delete --snapshots crn:v1:staging:public:is:us-south:a/efe5afc483594adaa8325e2b4d1290df::snapshot:r134-c4ea5585-0554-40db-bdc8-1ec9fb15098b,crn:v1:staging:public:is:us-south:a/efe5afc483594adaa8325e2b4d1290df::snapshot:r134-c10755ee-db71-472e-bf80-01e21229fda0