vania-janet/multiturn-rag-retrieval-data huggingface dataset:
: See [Working with apps in Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-application-workloads) and [Working with jobs and job runs](https://cloud.ibm.com/docs/codeengine?topic=codeengine-job-plan).

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





 20 July 2021 

Review the release notes for 20 July 2021.

New region!
: Code Engine is supported in a new region: Canada Toronto (ca-tor). See [Regions for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-regions).





 15 July 2021 

Review the release notes for 15 July 2021.

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

Subscription ping limits
: Added information about limits for subscription ping data. See [Subscription ping limits](https://cloud.ibm.com/docs/codeengine?topic=codeengine-limitssubscription-cron-limit).

Applications that use WebSockets
: Added information about apps that use WebSockets need to reconnect before the session expires. See [Do Code Engine apps support WebSockets](https://cloud.ibm.com/docs/codeengine?topic=codeengine-faqsapp-websockets)?

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





 7 July 2021 

Review the release notes for 7 July 2021.

Environment variables
: Updated information about automatically injected environment variables for Code Engine apps and jobs.
You might have extra charges from your provider. See to your carrier or service provider for their fee information.







 What is planned for Direct Link on Classic Exchange? 

The marketplace has evolved since Direct Link Exchange was established. With data center operators now blurring the lines as network service providers, IBM will be combining the Exchange offering with Connect on the new "next generation" platform to reflect both this change and simplify the Direct Link portfolio. Direct Link Exchange will service only the Direct Link classic infrastructure. After migrations of the partner inter-connections to the XCRs are complete, Exchange will be moved to End of Marketing (EoM).





 Will Direct Link be available in non-MZRs, or is it only a solution for MZRs? 

Initial rollout plans are for the Multi-Zone Regions (MZRs) to be prioritized. Other PoPs across the portfolio will support the new Direct Link access model, enabling access to the classic infrastructure and VPC expansions as they occur.





 If Direct Link is not available for single-campus multizone regions, how do financial services clients handle the data that they need to keep in their regions? 

Any existing customers on classic IaaS can remain in classic IaaS and continue to access classic IaaS data centers using Direct Link or IBM Cloud Direct Link on Classic. VPC connectivity is fully supported ONLY on Direct Link.





 Where are the Direct Link offerings enabled? 

For the most up-to-date information, see [Direct Link Dedicated](https://cloud.ibm.com/docs/dl?topic=dl-how-to-order-ibm-cloud-dl-dedicateddedicated-locations) and [Direct Link Connect](https://cloud.ibm.com/docs/dl?topic=dl-how-to-order-ibm-cloud-dl-connectconnect-locations) locations.





 How do I interconnect the classic infrastructure and VPC? 

You can connect the classic infrastructure and VPC with classic peering as described in [Setting up access to your Classic Infrastructure from VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-setting-up-access-to-classic-infrastructure).
It keeps track of your analysis and provides options for next steps. It also provides a count of the number of documents that match your current state of analysis. In this small collection, the number of documents relating to the Hill Walker is only 51. In a production data set, the number would usually be much larger. Analyzing trends and anomalies is often a good way to start as it allows you to see if anything seems out of the ordinary.

Immediately, you notice that the Hill Walker has problems in December and January. You decide to investigate further by narrowing this initial exploration to just the month of December.

Notice how the navigation view at the top always keep you informed of where you are in your analysis. Next, you select Analyze cause and characteristics because you are interested in why things are happening.

You notice that words like 'snow' and 'brake' are highlighted together (in the Part of Speech section), so you add these to your analysis.

The Content Miner project has narrowed your investigation to a small number of complaints that can be easily read. (clicks Show Documents)

The common theme here is that there is an unexpected problem with the way the brakes are working in snowy conditions. You now have the information you need to ask the engineering department to perform a detailed inspection of the braking system and determine why it is not working as expected in snowy conditions.

In this demonstration, you saw how a citizen analyst using Watson Discovery and content mining can easily discover hidden meaning in unstructured text. (list of features, functionality, and use cases)

What will you do with Watson Discovery? (Music outro)







 How it works 

To analyze your data, you use facets. Facets give you a way to slice your data and visualize a subset of information so it is easier to comprehend.

From the data analysis page for your collection, you can choose for the data to be shown in one of the following views:

Facets
: Shows facets that are derived from from annotations that are added to your documents by enrichments that are applied to your documents. Enrichments can include built-in Natural Language Processing enrichments, such as Part of Speech or Entities.
: Before updating to 2012, if you have an active/passive BGP over a High Availability GRE setup, ensure that you confirm your GRE interfaces have local-ip set to a VRRP virtual address instead of the main address configured on the dp0bond0 or dp0bond1 interfaces. You should also validate that your routing does not rely on the tunnel (tun) interface changing status to A/D or u/u on failover, as that will no longer occur. In those instances, IBM may recommend setting up a path monitoring policy for the remote GRE endpoint. This utilizes a ping health check to validate the path over the tunnel before adding a route to that tunnel's routing table. Open a [support case](https://cloud.ibm.com/docs/virtual-router-appliance?topic=gateway-appliance-getting-help) if you have questions about your configuration or if you want more information on path monitoring policies.





 Upgrading from 1801 to 2012 

Along with all previously listed issues for 1801 to 1912 and 1912 to 2012, you might encounter this issue when upgrading from 1801 to 2012:

After the update, the Vyatta boots, but the configuration is wiped.
: As a precautionary measure, before updating, set the time zone to 'UTC'. Some time zones from 1801 are not working in 2012 and may be causing this. For example, in 1801, time zones are listed as "Americas/Chicago" instead of "America/Chicago" in 2012.





 Vbash issues in older 5.2 Upgrades 

Occasionally, after a successful upgrade and reboot of a new version of the Vyatta OS, you might encounter a problem where you cannot issue user commands.

For example:

[jmathews@shelladmindal0101 ]$ ssh 10.115.174.6 -l vyatta
Welcome to AT&T vRouter

Welcome to AT&T vRouter
Version: 5.2R6S5
Description: AT&T vRouter 5600 5.2R6S5
Last login: Fri Feb 2 12:42:45 2018 from 10.0.80.100
Select the [location](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-regions) where you plan to provision the instance.
6. Enter a name for the service instance.
7. Select a resource group.

By default, the Default resource group is set.

Note: If you are not able to select a resource group, check that you have editing permissions on the resource group where you want to provision the instance.
8. Select the Lite service plan.

By default, the lite plan is set.

For more information about other service plans, see [Pricing plans](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-service_plans).
9. Click Create.



After you provision an instance, the Logging dashboard opens.

Next, configure a log source by adding a logging agent. This agent is responsible for collecting and forwarding logs to your instance.





 Configuring your instance to be accessible to private endpoints only 

After provisioning your instance through the Observability dashboard or catalog, you can configure the instance to be accessibile by private endpoints only.

If you configure your instance to use private endpoints only, this will block the public endpoints. All ingestion and API usage that may be in progress on the public endpoints will be blocked when the configuration change is made.

Unless otherwise specified when provisioning an instance, the default is for the instance to be accessible by both public and private endpoints.



1. [Log in to your IBM Cloud account](https://cloud.ibm.com/login).

After you log in with your user ID and password, the IBM Cloud dashboard opens.
2. Click the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/icons/icon_hamburger.svg) > Observability.
3.
FAQs for Continuous Delivery 

Get answers to frequently asked questions about using IBM Cloud® Continuous Delivery.



 My Continuous Delivery service states that Lite plan services are deleted after 30 days of inactivity. What does inactivity mean? 

An instance of the Continuous Delivery service is considered active when one or more of the toolchains within the same resource group is active. A toolchain is considered active if users interact with it by way of the user interface, delivery pipeline jobs are triggered, or repositories that are managed by Git Repos and Issue Tracking are accessed. To be considered inactive, all of these conditions must be absent for all of the toolchains that are associated with the Continuous Delivery service, for 30 days.





 I tried to deploy an app to IBM Cloud, why am I getting an error? 

When trying to deploy an app to IBM Cloud, if you get the following error message, the amount of memory that is remaining in your organization is less than the amount of memory that is required by the app that you want to deploy.

FAILED Server error, status code: 400, error code: 100005, message: You have exceeded your organization's memory limit.

You can either increase the memory quota of your account or reduce the memory that your apps use. The maximum memory quota for a trial account is 2 GB. To increase the memory quota of your account, convert your trial account to a pay account. For information about how to convert your trial account to a pay account, see [How do I upgrade or change my account?](https://cloud.ibm.com/docs/account?topic=account-accountfaqschangeacct). To reduce the memory that your apps use, use either the IBM Cloud console or the cf command line interface.

If you use the IBM Cloud console, complete the following steps:



1. In the Apps Dashboard, select your app. The app details page opens.
2. In the runtime pane, you can reduce the maximum memory limit or the numbers of app instances, or both, for your app.



If you use the cf command line interface, complete the following steps:



1. Check how much memory is being used for your apps.
Select Everything to see all the events, or a view.



You can view events through the view that you have selected.





 View a subset of the events by applying a search query 

You can select the events that are displayed through a view by applying a search query. You can save that view for reuse later. [Learn more](https://cloud.ibm.com/docs/services/activity-tracker?topic=activity-tracker-viewsviews_step2).





 View a subset of the events by applying a timeframe 

You can select the events that are displayed through a view by applying a timeframe.

You can apply a timestamp by specifying an absolute time, a relative time, or a time range.

Complete the following steps to jump to a specific time:



1. [Go to the web UI](https://cloud.ibm.com/docs/services/activity-tracker?topic=activity-tracker-launchlaunch).
2. Click the Views icon ![Views icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/views.png).
3. Select Everything or a view.
4. Enter a time query. Choose any of the following options:



* Enter an abosute time to jump to a point in time in your events such as May 20 7:00pm.
* Enter a relative time such as 2 days ago, today at 12am, or an hour ago.
* Enter a time range such as yesterday 10am to yesterday 11am, last fri 4:30pm to 11/12 1 AM, last wed 4:30pm to 23/05 1 AM, or May 20 10am to May 22 10am. Make sure to include to to separate the initial timestamp from the end timestamp.



5. Press ENTER.

You might get the error message: Your request is taking longer than expected, try refreshing your browser in a bit as we try to catch up. Retry.
If there is no guideline, consider starting one. The first entry can address the question you are debating now, and can describe the resolution that you come to. This entry will save time for the next human annotator who stumbles upon the same issue.
* Discuss the question with other human annotators involved in the workspace, and try to decide together on the optimal solution. This type of discussion is expected and beneficial to the workspace overall. It will encourage you to all follow the same methodology as you annotate the documents.







 Related information 



* [Annotating documents](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-user-guide)
* [Dictionaries](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-dictionaries)
* [Type systems](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-typesystem)
ibmcloud resource service-instance-update <service_instance_name>
--service-plan-id <plan_id>









 Delivery Pipeline usage 

Delivery pipelines under a Continuous Delivery service instance Lite plan have several limitations.



* The 500-step and job run limit includes both pipeline steps for Tekton pipelines and pipeline job runs for Classic pipelines. If your pipeline has many steps within a single run, such as with the DevSecOps pipelines, you might reach this limit quickly.
* Delivery pipeline failures, excluding skipped step runs and Classic job runs, are counted as part of the 500 Tekton step run limit per month. This 500-step run limit also applies to Classic job runs for Classic pipelines.
* All of your toolchains and all of your pipelines within those toolchains that are in the same resource group contribute to the same limit of 500 Tekton step runs per month. The same limit is used because pipeline step runs and job runs are counted at the resource group level for a specific Continuous Delivery instance.



A five-day grace period is offered the first time that you reach the 500-step run limit. This grace period is offered only once.

The retention period for pipelines varies based on the pipeline type and the plan that is selected for the Continuous Delivery service instance.



* Classic pipelines retain a maximum of 10 stage runs on either plan.
* Tekton pipelines under the Professional plan retain PipelineRuns and their logs for one year.
* Tekton pipelines under the Lite plan retain PipelineRuns and their logs for 30 days.



The acceptable usage behaviors include, but are not limited to, these behaviors:



* The compilation and assembly of artifacts for supported programming languages.
* The automated deployment of application artifacts, configurations, and supporting resources or services.
* Testing, validation, and other development event-generated behavior that is triggered as the result of a development process.



The usage behaviors that are not permitted include, but are not limited to, these behaviors:



* The use of pipeline jobs or workers for general compute behaviors, such as Bitcoin mining, distributed denial-of-service attacks, and malicious or offensive behavior to other clients or users within the IBM Cloud platform or general internet users.
These words are now extracted from the highlights, rather than simply displaying the first 50 words of the article. See [highlight](https://cloud.ibm.com/docs/discovery?topic=discovery-query-parametershighlight) for an explanation of highlights. Highlights do not need to be explicitly included in your query to enable this behavior.





 25 September 2018 

New Continuous Relevancy Training feature : Released Continuous Relevancy Training, which uses interactions from users to learn how to surface the most relevant results. It can learn from user behavior automatically, significantly reducing the effort required to improve the relevancy ranking of results. See [Continuous Relevancy Training](https://cloud.ibm.com/docs/discovery?topic=discovery-crt) for details.

New API support for longer queries : Added API support for performing longer queries. This increases the character limit to 10,000 characters, and makes it possible to increase the number of filters in your queries and perform more complex aggregations. See the POST Query at [API reference](https://cloud.ibm.com/apidocs/discoverylong-collection-queries) and [API reference](https://cloud.ibm.com/apidocs/discoverylong-environment-queries) for details.

Improved ability to upgrade to Advanced plan : You can now upgrade your Advanced plan using the API. See [Upgrading your plan](https://cloud.ibm.com/docs/discovery?topic=discovery-upgrading-your-planswitchadvanced) for details.

New Element Classification objects : The Element Classification enrichment now has updated classified elements, contract elements, and parties and tables identified. For the updates, see [Element Classification](https://cloud.ibm.com/docs/discovery?topic=discovery-element-classification).

New full support for Brazilian Portuguese : Added full support for the Brazilian Portuguese language. For more information, see [Language support](https://cloud.ibm.com/docs/discovery?topic=discovery-language-support).
For more information, see [Adding orgs and spaces](https://cloud.ibm.com/docs/account?topic=account-orgsspacesuserscreateorg).





 Why do I get logged out of my account? 

The administrator of your account has customized the duration of active and inactive accounts, which requires users to enter their credentials after a specific time. For more information, see [Managing user's login session durations](https://cloud.ibm.com/docs/account?topic=account-iam-work-sessions).





 Why can't I create a Lite account? 

Based on an update to our account registration that released starting 25 October 2021, new accounts are created as Pay-As-You-Go. As part of this update, you're asked to provide credit card information for identity verification. After you register and create your new account, you can access the full IBM Cloud catalog, including all Free and Lite plans. And, you get a $200 credit that you can use on products in the first 30 days. You pay only for billable services that you use, with no long-term contracts or commitments.

If you created a Lite account before 25 October 2021, you can continue working as you always have. However, you can go ahead and [upgrade to a Pay-As-You-Go account](https://cloud.ibm.com/docs/account?topic=account-accountfaqschangeacct) by adding your credit card information. This way, you can gain access to all Free service plans in the catalog.





 How do I see who created a service instance and when? 

From the [Resource list](https://cloud.ibm.com/resources), expand the appropriate section, and click the row for the instance that you want more details about. Additional details about the resource display including when the resource was created and by whom.

For classic infrastructure services, you can get similar information by using the [Audit log](https://cloud.ibm.com/docs/account?topic=account-audit-log).
When Emphasize the answer is used ("find_answers": true), Discovery rescores and reorders the documents to ensure that documents with the highest-quality answers are returned first.





 Choosing a project type 

If the Conversational Search project type isn't providing the best answers and you want to understand why, switch to using a Document Retrieval project type.

Most often, the Conversational Search project type is the right choice. You get great results from the start, and when you enable extra features like Emphasize the answer, the answers are clear and concise. However, for advanced use cases, or if you want to be able to troubleshoot issues, a Document Retrieval project type might be a better fit.

To help you choose the right Discovery project type, review the project type differences that are described in the following table.



Project type details

 Function Conversational Search Document Retrieval 

 Enrichment support Only the Part of Speech enrichment is applied. The Part of Speech and Entities enrichments are applied. The Entities enrichment is helpful for identifying important information and introduces more ways to filter query results. 
 Testing queries from the Improve and customize page in Discovery You see only one of the responses that are returned from the chatbot. You cannot see all of the available responses and cannot analyze individual query results. You can filter query results by enrichment-based facets. You can review details about fields that are indexed in the source documents that are returned for a query. Access to more information makes it easier to troubleshoot unexpected results. 
 Search triggers Returns answers from the text field automatically. If answers are stored in another field, you must change the configuration. You can apply a Smart Document Understanding (SDU) model or enrichments to your collections and retrieve useful information from fields other than text when search is triggered from the assistant. 



For both project types, the best way to test is to trigger search from the Watson Assistant preview. When you configure search support for an assistant, you can fine-tune the experience in ways that aren't available in Discovery.

And settings that are available from the Search results tool for a Document Retrieval project type are replaced by configuration settings that you specify in Watson Assistant. For example, the query response title and body are defined in Watson Assistant.
Switching between new and classic experiences 

You can easily switch back and forth between the new experience and the classic experience. However, the new experience provides a simplified user interface, an improved deployment process, and access to the latest features. For more information, see [Migrating to the new experience](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-migrate-overview).

To switch between the new and classic experiences, following these steps:



1.  From the Watson Assistant interface, click the Manage![Manage icon](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/user-icon.png) icon to open your account menu.
2.  Select Switch to classic experience or Switch to new experience from the account menu.



You won't lose any work if you switch to a different experience, and other users of the same instance are not affected. However, keep in mind that any work you do in one experience is not available in the other experience. You can switch back and forth at any time.