vania-janet/multiturn-rag-retrieval-data huggingface dataset:
":"delay","t0":2240},{"duration":2240,"memory_slot":0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26],"name":"acquire","qubits":0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26],"t0":0}]},{"name":"measure","qubits":17],"sequence":{"ch":"m17","label":"M_m17","name":"parametric_pulse","parameters":{"amp":0.059954379699145625,0.34482672801697584],"duration":2240,"sigma":64,"width":1984},"pulse_shape":"gaussian_square","t0":0},{"ch":"m17","duration":1616,"name":"delay","t0":2240},{"duration":2240,"memory_slot":0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26],"name":"acquire","qubits":0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,
* Determines whether the date/time value is after or the same as the date/time argument.
* Analogous to .after().







 .sameOrBefore(String date/time) 



* Determines whether the date/time value is before or the same as the date/time argument.







 today() 

Returns a string with the current date in the format yyyy-MM-dd.



* Static function.
* The other date methods can be invoked on date values that are returned by this function and it can be passed in as their argument.
* If the context variable $timezone is set, this function returns dates in the client's time zone. Otherwise, the GMT time zone is used.



Example of a dialog node with today() used in the output field:

{
"conditions": "what_day_is_it",
"output": {
"generic": [
{
"values":
{
"text": "Today's date is <? today() ?>."
}
],
"response_type": "text",
"selection_policy": "sequential"
}
]
}
}
Show more

Result: Today's date is 2018-03-09.







 Date and time calculations 

Use the following methods to calculate a date.



 Method Description 

 <date>.minusDays(n) Returns the date of the day n number of days before the specified date. 
 <date>.minusMonths(n) Returns the date of the day n number of months before the specified date. 
 <date>.minusYears(n) Returns the date of the day n number of years before the specified date. 
 <date>.plusDays(n) Returns the date of the day n number of days after the specified date. 
 <date>.plusMonths(n) Returns the date of the day n number of months after the specified date. 
 <date>.plusYears(n) Returns the date of the day n number of years after the specified date.
"start_timestamp": "2021-10-12T20:54:06.321Z",
"stop_timestamp": "2021-10-12T20:54:14.338Z",
"response_milliseconds": 535
}
},
{
"type": "enable_speech_barge_in"
},
{
"type": "text_to_speech",
"barge_in_occurred": true,
"streaming_statistics": {
"transaction_id": "eafdd846-2829-4e1a-8068-b1035510b1e1",
"start_timestamp": "2021-10-12T20:54:14.795Z",
"stop_timestamp": "2021-10-12T20:54:20.388Z",
"response_milliseconds": 447
}
}
]
},
{
"assistant": {
"log_id": "07d74b35-0205-43e4-923c-1e43e1cb429c",
"response_milliseconds": 0,
"start_timestamp": "2021-10-12T20:54:20.377Z"
},
"request": {
"type": "hangup"
},
"response": ]
}
]
}
]
}

Show more

For detailed information about the structure of the CDR event payload, see [CDR log event reference](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-cdr-log-reference).
Rendel, Asaf, Raul Fernandez, Ron Hoory, and Bhuvana Ramabhadran. [Using Continuous Lexical Embeddings to Improve Symbolic-Prosody Prediction in a Text-to-Speech Front End.](https://ieeexplore.ieee.org/document/7472760) Proceedings ICASSP (2016), pp. 5655-5659.
12. Shechtman, Slava. [Maximum-Likelihood Dynamic Intonation Model for Concatenative Text to Speech System.](http://www.isca-speech.org/archive_open/archive_papers/ssw6/ssw6_234.pdf) Proceedings of the Sixth ISCA Workshop on Speech Synthesis (August 2007): pp. 234-239.
13. Shuang, Zhi-Wei, Raimo Bakis, Slava Shechtman, Dan Chazan, and Yong Qin. [Frequency warping based on mapping formant parameters.](https://www.researchgate.net/profile/Slava_Shechtman/publication/221491579_Frequency_warping_based_on_mapping_formant_parameters/links/55d462dd08ae7fb244f60c61.pdf) Proceedings of the Ninth International Conference on Spoken Language Processing (ICSLP), Interspeech (2006): pp. 2290-2293.
Submitting request to restore resource reclamation 835bdb40-b33b-43b4-a1f6-e234433334 under account
OK
Request to restore reclamation 835bdb40-b33b-43b4-a1f6-e234433334 was submitted

Issuing a ibmcloud resource reclamations will now show the service instnace in a RESTORING state

Example:

>$ ibmcloud resource reclamations
List all resource reclamations
OK
ID Resource Instance ID Entity CRN State Target Time
835bdb40-b33b-43b4-a1f6-e234433334 d670d057-34c2-4430-8071-bafb0dfddse108 crn:v1:bluemix:public:dashdb-for-transactions:us-south:a/a8a1951114b2d2esddf59d2d01:d670d057-34c2-4430-8071-ba23443108:: RESTORING 2021-10-27T14:08:22Z

Once the service instance has been restore it will appear in Resources under Services and software on the IBMCloud dashboard.
(https://www.researchgate.net/publication/295080074_Using_Deep_Bidirectional_Recurrent_Neural_Networks_for_Prosodic-Target_Prediction_in_a_Unit-Selection_Text-to-Speech_System) Proceedings Interspeech (2015), pp. 1606-1610.
5. Fernandez, Raul, Asaf Rendel, Bhuvana Ramabhadran, and Ron Hoory. [Prosody Contour Prediction with Long Short-Term Memory, Bi-directional, Deep Recurrent Neural Networks.](https://www.researchgate.net/publication/267154161_Prosody_Contour_Prediction_with_Long_Short-Term_Memory_Bi-Directional_Deep_Recurrent_Neural_Networks) Proceedings Interspeech (2014), pp. 2268-2272.
6. Fernandez, Raul, Zvi Kons, Slava Shechtman, Zhi Wei Shuang, Ron Hoory, Bhuvana Ramabhadran, and Yong Qin. [The IBM Submitted to the 2008 Text-to-Speech Blizzard Challenge.](http://festvox.org/blizzard/bc2008/ibm_Blizzard2008.pdf) Blizzard Challenge Workshop 2008.
7. Fernandez, Raul, and Bhuvana Ramabhadran. [Automatic Exploration of Corpus-Specific Properties for Expressive Text-to-Speech: A Case Study in Emphasis.](http://www.isca-speech.org/archive_open/archive_papers/ssw6/ssw6_034.pdf) Proceedings of the Sixth ISCA Workshop on Speech Synthesis (August 2007): pp. 34-39.
8. Fernandez, Raul, Raimo Bakis, Ellen Eide, Wael Hamza, John Pitrelli, and Michael A. Picheny. [The 2006 TC-STAR Evaluation of the IBM Expressive Text-to-Speech Synthesis System.]
","t0":0},{"ch":"m8","duration":1616,"name":"delay","t0":2240},{"ch":"m9","label":"M_m9","name":"parametric_pulse","parameters":{"amp":0.2518119385912279,0.12243670847800485],"duration":2240,"sigma":64,"width":1984},"pulse_shape":"gaussian_square","t0":0},{"ch":"m9","duration":1616,"name":"delay","t0":2240},{"duration":2240,"memory_slot":0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26],"name":"acquire","qubits":0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26],"t0":0}]},{"name":"measure","qubits":1],"sequence":{"ch":"m1","label":"M_m1","name":"parametric_pulse","parameters":{"amp":0.1570406590513299,-0.19452051666784137],"duration":
</GlacierJobParameters>
</RestoreRequest>

Sample Response

HTTP/1.1 202 Accepted
Date: Wed, 7 Feb 2018 19:51:00 GMT
Connection: close



* Java
* Python
* Node



public RestoreObjectRequest(String bucketName,
String key,
int expirationInDays)

response = client.restore_object(
Bucket='string',
Key='string',
RestoreRequest={
'Days': 123,
'GlacierJobParameters': {
'Tier': 'string'
},
}
)

var params = {
Bucket: 'STRING_VALUE', /* required /
Key: 'STRING_VALUE', /* required /
ContentMD5: 'STRING_VALUE', /* required /
RestoreRequest: {
Days: 1, /* days until copy expires /
GlacierJobParameters: {
Tier: 'STRING_VALUE' /* required /
},
}
};
s3.restoreObject(params, function(err, data) {
if (err) console.log(err, err.stack); // an error occurred
else console.log(data); // successful response
});

Method Summary



 Method Description 

 clone() Creates a shallow clone of this object for all fields except the handler context. 
 getBucketName() Returns the name of the bucket containing the reference to the object to restore. 
 getExpirationInDays() Returns the time in days from an object's creation to its expiration. 
 setExpirationInDays(int expirationInDays) Sets the time, in days, between when an object is uploaded to the bucket and when it expires. 



--------------------





 Get an object's headers 

A HEAD given a path to an object retrieves that object's headers.
The relationship between the date and time values is established in two ways:



* Each entity that participates in the relationship contains the same datetime_link attribute.
* The literal string that spans the complete date and time mention, when they are mentioned together in input, is the same for both entities. The location information is appended to the datetime_link name.





 Recognized formats 



* now
* two hours from now
* on Monday at 4pm







 Attributes 



* .datetime_link: If present, indicates that the user's input mentions a date and time together, which implies that the date and time are related to one another. The start and end index values of the string that includes the date and time are saved as part of the link name.



The following table illustrates the information that each attribute captures from the user input.



Date and time attributes

 Attribute Type Example 

 @sys-date.datetime_link and @sys-time.datetime_link string If the input is, Are you open today at 5?, then today is recognized as a date mentionn(2020-05-21) at location [13,18] and at 5 is recognized as a time mention (05:00:00) at location [19,23]. A location value of [13,23], which spans both the date and time mentions, is appended to the resulting datetime_link. It is named datetime_link_13_23 and it is included in the output of the @sys-date and @sys-time entities that participate in the relationship. 







 Time zones 

Mentions of a date or time that are relative to the current time are resolved for a chosen time zone. By default, the time zone is Greenwich mean time. Therefore, REST API clients that are located in different time zones get the current Coordinated Universal Time when now is mentioned in input.

Optionally, the REST API client can add the local time zone as the context variable $timezone. This context variable must be sent with every client request. For example, the $timezone value can be America/Los_Angeles, EST, or UTC.
{
"output": {
"generic": [
{
"values":
{
"text": "The current date and time is: <? now('Europe/London') ?>"
}
],
"response_type": "text",
"selection_policy": "sequential"
}
]
}
}

You can substitute the hard-coded time zone value with a context variable to dynamically change the time based on a time zone that is passed to the expression. For example: <? now('$myzone') ?>. The $myzone context variable might be set to 'Australia/Sydney' in one conversation and to 'Mexico/BajaNorte' in another.





 .reformatDateTime(String format) 

Formats date and time strings to the format desired for user output.

Returns a formatted string according to the specified format:



* MM/dd/yyyy for 12/31/2016
* h a for 10pm



To return the day of the week:



* E for Tuesday
* u for day index (1 = Monday, ..., 7 = Sunday)



For example, this context variable definition creates a $time variable that saves the value 17:30:00 as 5:30 PM.

{
"context": {
"time": "<? @sys-time.reformatDateTime('h:mm a') ?>"
}
}

Format follows the Java [SimpleDateFormat](http://docs.oracle.com/javase/6/docs/api/java/text/SimpleDateFormat.html) rules.

When trying to format time only, the date is treated as 1970-01-01.





 .sameMoment(String date/time) 



* Determines whether the date/time value is the same as the date/time argument.







 .sameOrAfter(String date/time) 



* Determines whether the date/time value is after or the same as the date/time argument.
* Analogous to .after().
- The effective_dates, contract_amounts, and termination_dates arrays now each include a confidence_level field that indicates a value of High, Medium, or Low.

For more information, see [Classifying elements](https://cloud.ibm.com/docs/discovery?topic=discovery-output_schema) and [Parsing contracts](https://cloud.ibm.com/docs/discovery?topic=discovery-contract_parsing). : The Discovery tooling does not yet use the current API version: 2019-01-01 (it currently uses 2018-12-03), so you cannot see these new fields in the Element Classification output in the Discovery tooling.





 10 January 2019 

Known issue for customer-id : If you specify a customer-id, using the normalization method described in [Specifying a customer_id](https://cloud.ibm.com/docs/discovery?topic=discovery-sourcessource_customer_id) and subsequently attempt to delete documents containing that customer_id, using the method described in [Deleting labeled data](https://cloud.ibm.com/docs/discovery?topic=discovery-information-securitydeletingdata), the associated source document is not deleted.





 1 January 2019 

Update to version string : The version string for all API calls changed to 2019-01-01 from 2018-12-03. This version introduces a new document ingestion status: pending. The pending status is returned for documents that are accepted but did not yet start processing. Previously, these documents had the status of processing. The Discovery tooling does not yet use this API version (it currently uses 2018-12-03), so when you check document status in the Discovery tooling, the pending status is not returned.





 21 December 2018 

New option to connect and sync with Microsoft Sharepoint 2016 On-Premise : Added the option to connect to and sync with Microsoft SharePoint 2016 On-Premise. This data source is not available in Dedicated environments. See [SharePoint 2016 On-Premise](https://cloud.ibm.com/docs/discovery?topic=discovery-sourcesconnectsp_op) for more information.
string_equals<br><br>[1] String The property value is an exact match to the condition value. Yes 
 string_not_equals<br><br>[2] String The property value is not an exact match to the condition value. Yes 
 string_match String The property value matches the condition value by using the [Krauss wildcarding algorithm](https://en.wikipedia.org/wiki/Krauss_wildcard-matching_algorithm). Yes 
 string_not_match String The property value does not match the condition value by using [Krauss wildcarding algorithm](https://en.wikipedia.org/wiki/Krauss_wildcard-matching_algorithm). Yes 
 string_contains String The property value contains part of the condition value. Yes 
 string_not_contains String The property value contains part of the condition value. Yes 
 <br>Deprecated<br><br>strings_in_list<br><br>[3] String list All property values are in the condition value list. Yes 
 strings_allowed<br><br>[4] String list All property values are in the condition value list. Yes 
 strings_required<br><br>[5] String list All condition values are in the property value list. Yes 
 ips_in_range<br><br>[6] IP list All property values, in IPv4 or IPv6 format, are in the condition value list. Yes 
 ips_equals<br><br>[7] String The property value is an exact match to the condition value. Yes 
 ips_not_equals<br><br>[8] String The property value is not an exact match to the condition value. Yes 
 num_equals<br><br>[9] Numeric The property value numerically matches to the condition value. Yes 
 num_not_equals<br><br>[10] Numeric The property value does not numerically match the condition value. Yes 
 num_less_than Numeric The property value is numerically less than the condition value.
For more information about each version, see [Comparing /v1/policies and /v2/policies syntax](https://cloud.ibm.com/docs/account?topic=account-known-issuescompare-syntax).



Table 3. The string comparison operators available for conditions in access policies.

 Operator Description 

 stringEquals Case-sensitive string comparison. Boolean or number values are converted into a string before comparison. 
 stringMatch Case-sensitive string match is performed between the pattern and the target string by using either an asterisk (), question mark (?), or both. An asterisk () represents any sequence of zero or more characters in the string, and a question mark (?) represents any single character. You can also express an asterisk * and question mark ? as a literal value by enclosing each within two sets of curly brackets {{}}. 
 stringExists String must be present but can have any none zero value. 
 stringEqualsAnyOf Case-sensitive exact string matching any of the strings in an array of strings. 
 stringMatchAnyOf Case-sensitive string matching any of the strings in an array of strings. The values can include a multi-character wildcard (), which matches any sequence of zero or more characters, a single-character wildcard (?), matching any single character, or both. You can also express an asterisk * and question mark ? as a literal value by enclosing each within two sets of curly brackets {{}}. 



For example, the following statement contains an operator element that uses stringEquals to specify that the account ID and service name must exactly match the value element. The statement also contains an operator element that uses stringMatch to specify a naming pattern for Event Streams topics that you might use to organize access to those specific resources. This way, you can assign one policy to all topics in your account that begin with messagehub-topic-dev.

"resource": {
"attributes": [
{
"operator": "stringEquals",
[6]



 Response format 

For responses, a float field SHOULD be documented as either a 32-bit float or a 64-bit double and MAY further constrain the range of valid values. For the sake of backward-compatible future expansions, documented constraints MAY be more permissive (allowing for a larger range of values) for responses than for requests.

A float value MUST be returned as a JSON number and MAY have a decimal point or use scientific notation.



Schema guidance for floats in responses

 Constraint Recommended value Description 

 type number type MUST be number. 
 format float or double format MUST be float or double. 
 minimum minimum value MAY be present. 
 maximum maximum value MAY be present. 







 Request formats 

For requests, a float field MUST document and enforce support for either a 32-bit float or a 64-bit double and MAY further constrain the range of valid values.

Minimum and maximum constraints MUST be checked prior to any other processing of a float included in a request. Failure to match constraints MUST cause the entire request to fail with a 400 status code and appropriate error response model.



 Request bodies 



* Any JSON number value MUST be considered a valid float, but MAY be rejected by other validation rules.
* The null JSON keyword MAY be accepted in a JSON merge patch request body if the field is optional in the resource state and MUST NOT be accepted otherwise.
* Any other value MUST be rejected with a 400 status code and appropriate error response model.







 Query parameters 



* Any string containing a [valid JSON number](https://datatracker.ietf.org/doc/html/rfc7159section-6) value MUST be considered a valid float.
* The lowercase string null MUST be considered a match for a value absent from the observable resource state.
* Any other string MUST be considered invalid and SHOULD be rejected with a 400 status code and appropriate error response model.





Schema guidance for floats in requests

 Constraint Recommended value Description 

 type number type MUST be number. 
 format float or double format MUST be float or double. 
 minimum minimum value MAY be present. 
 maximum maximum value MAY be present. 











 String 

The string type provides for arbitrary strings of characters.
If the threshold is met, the pattern is considered to match, and the function that uses the matcher returns the observations that correspond to the pattern; otherwise, the function returns null.

TS_MATCHER_SUBSET_PM(Double) Output: MatcherType
Creates a matcher that matches an array of string values (the pattern) with a string time series, regardless of the order in which the items in the pattern occur in the time series. The specified coverage threshold is a double-precision number in the range 0.0 - 1.0 that indicates the minimum ratio of pattern size to match string size. For example, a threshold of 0.75 means that the specified pattern must match at least 75% of the match string, in sequence but not necessarily contiguously. If the threshold is met, the pattern is considered to match, and the function that uses the matcher returns the observations that correspond to the pattern; otherwise, the function returns null.

TS_MATCHER_SUBSET_MS(Double) Output: MatcherType
Creates a matcher that matches an array of string values (the pattern) with a string time series, regardless of the order in which the items in the pattern occur in the time series. The specified coverage threshold is a double-precision number in the range 0.0 - 1.0 that indicates the minimum ratio of match string size to sequence size. For example, a threshold of 0.75 means that the specified pattern must match at least 75% of the match string, in sequence but not necessarily contiguously. If the threshold is met, the pattern is considered to match, and the function that uses the matcher returns the observations that correspond to the match string; otherwise, the function returns null.
For requests, a string field MUST have documented minimum and maximum lengths and MUST have a documented permissible character set. A string field that does not contain completely free-form values SHOULD have a documented regular expression pattern which values are required to match.

Length, character set, and pattern constraints MUST be checked prior to any other processing of strings included in requests. Failure to match constraints MUST cause the entire request to fail with a 400 status code and appropriate error response model.

A free-form string field (such as a description or notes field) that allows a zero-length value SHOULD be optional in a request body, and if it is optional, its default value MUST be a literal empty string ("").

A zero-length string value MUST NOT be accepted to use a default or computed value or to omit a field entirely from observable resource state. For example, if a request has an optional public_ip_address field and omitting or providing a null value (in a JSON merge patch request) for the field results in a resource without a public IP address, providing a zero-length value MUST NOT do the same.



Schema guidance for strings in requests

 Constraint Recommended value Description 

 type string type MUST be string. 
 minLength minLength MUST be present. 
 maxLength maxLength MUST be present. 
 pattern pattern SHOULD be present unless character constraints cannot be expressed in a regular expression. 









 Date 

The date type specifies a particular year, month, and day.



 Response format 

A date value MUST be returned as a JSON string containing a date in the format YYYY-MM-DD, matching the full-date format as [specified by RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339section-5.6).

In this format:



* YYYY is a four-digit year value
* MM is a two-digit month value (01-12)
* DD is a two-digit day-of-the-month value (01-31)





Schema guidance for dates in responses

 Constraint Recommended value Description 

 type string type MUST be string. 
 format date format MUST be date. 







 Request formats
-0.005701605696231127,-0.0011209178483113647],-0.005779513623565435,-0.001136234262958169],-0.005856579169631004,-0.0011513851350173354],-0.0059327553026378155,-0.0011663611512631178],-0.006007994990795851,-0.00118115299846977],-0.006082251202315092,-0.0011957515962421894],-0.006155477836728096,-0.00121014763135463],-0.0062276278622448444,-0.001224332139827311],-0.0062986561097204685,-0.00123829604126513],-0.006368516478687525,-0.0012520304881036282],-0.006437164265662432,