New enhancements to Azure Machine Learning
vrijdag 24 oktober 2014
- Join: In the case of joining tables, adding columns to tables, or loading tables from sources that allow duplicate column names, columns with the same name as a column in the table ("My Column") are now renamed with a space and then the replication number: "My Column (2)", “My Column (3)", and so on. Previously there was no space between the column name and the number in parentheses. Experiments that select columns by name containing columns named under the old convention "My Column(2)" will need to be updated to reflect the new protocol "My Column (2)".
- Writer: For Azure Blob Storage data destination, a parameter Azure blob storage write mode was added.
- If the Overwrite option is selected, the blob file in destination will be overwritten, if it exists.
- If the Error option is selected and the blob file already exists, it will not be overwritten, but error message will still be shown.
- Metadata Editor: Able to convert string columns with missing values.
- Sweep Parameters: Results are sorted by the selected metric.
- Bayesian Linear Regression: Now processes string columns.
- Cross-Validate Model: Missing values were incorrectly being counted as false negatives. This issue has been fixed.
- Split Module: Now propagates column names in Recommender Split mode.
- Vowbal Wabbit Score: Unnecessary input parameters have been removed.
- When creating a new Azure Machine Learning workspace in the Azure Management Portal, the Workspace Owner is automatically populated with the Windows account (Live ID) with which you are signed in.
- The Owner of a workspace can now be changed from the Configure tab within the Azure Management Portal.
- The Open in Studio button on the command bar allows you to jump directly to the Azure Machine Learning Studio.
- When you click in the R Script parameter of the Execute R Script module, the parameter pane now expands so that the text box for editing your R script is larger.
- If you attempt to sign in to Azure Machine Learning with a Microsoft Account (Live ID) that does not have access to a workspace, the Microsoft Account is displayed to make troubleshooting easier when you have multiple Microsoft Accounts.
- For RRS API calls, error numbers for-user related errors will change from error number 500 to "400 Bad Request." The body of the error, which is in JSON format, will also have a Message property, which will contain the error message. An example of the modified error: