Download Matlab Connector

[Marcelo Chaplin]

Ihave a problem on my Mac OS X 10.11.5 Beta (15F31a), with MATLab R2016a (9.0.0.341360). When I install the MATLab Drive Connector from the website as matlabdrive.mlpkginstall or from the add-ons menu in MATLab itself, it works absolutely fine; it synchronises my files and displays its logo in the menu bar top-right, through which I can access its menu/settings/etc.

However, upon the second start-up of my computer; MATLab Drive Connector is no longer usable. When I open it; an empty menu space is created in my menu items; and when clicking on that space, it's marked as selected; but nothing else happens, nor are my files synchronised. When I have selected the MATLab Drive Connector to start at startup right after its installation, the empty space is immediately created, with the same effects. When MATLab Drive Connector is forcibly stopped via Activity Monitor; the empty space will disappear. I have attached a screen recording [1] of this issue.

EDIT:

however since two days, even when attempting to de/re-install, I get the error "The specified key is not present in the current container", as shown in the attached screenshot [2] preventing me from doing anything to fix this issue.

I had a similar issue under Win 10. Typically Connector can be started by clicking its icon in the MATLAB folder in the Start Menu. This however requires a confirmation of User Account Control (UAC). So one needs to eliminate that, so that it doesn't cause an issue on start-up.

The new Polarion Connector for Simulink allows for a much-improved user experience over earlier versions of the connector. For the first time, Polarion itself has been directly embedded into the Simulink desktop client to support a larger set of customer use cases and reduce inconvenient App context switching.

Working with the Simulink Requirements Toolbox

Also, another first for the new connector is that it will work with the Simulink Requirements Toolbox. Users can then use the popular drag-and-drop approach to create traceability between requirements and model elements. Then, depending on the connector settings, surrogate Simulink items can be created in Polarion for any linked model elements. These surrogate Simulink items are rich in information too with block parameter data and where applicable model diagrams. The integration automatically links the surrogate Simulink items back to the original Polarion Requirements as well.

Extending the supported use cases even further, users can work with Polarion Live Documents directly or across the entire Polarion project scope. When working with Polarion LiveDoc documents it is possible to work with document baselines or earlier revisions.

Backward compatibility with older releases of the connector

To maintain backward compatibility with earlier connector releases, the new connector also supports publishing and direct linking to existing Polarion Work Items and Requirements. This mode can work with or without surrogates Simulink items as well.

The connector allows you to execute Simulink Tests, collect results, and publish these back to Polarion in the form of a Test Run and Test Record. This can all be done directly from the connector control panel.

With adding support for Simulink Test, we can leverage Polarion's powerful Quality Management capabilities. Polarion becomes a one-stop place for all your Test Management and Test evidence of your Simulink models.

Changes for 3.1.0

New Features:

- Support the ability to map Polarion work-item types to Simulink requirement types (Functional, container, and informational)

- Added support for Polarion personal authentication tokens (PAT) for authentication with Polarion

- Added ability to customize how Simulink block information is presented and ordered in the Polarion surrogate item

- Added a new Start page configuration property to allow users to specify a start page URL for Polarion when Polarion first opens on the launch of the connector pane

- Added a new customizations folder to the installation that includes several customization scripts to support extended functionality. Please refer to the folder for more details

Fixes:

- SC-503 - There is an [syntax] error shown when the user defines several configurations for the same server URL and calls Polarion Context Selector

- SC-464 - Optimize "Open in Polarion" behavior not to refresh Polarion views on each request

- SC-492 - Improve behavior of progress indicator on loading of LiveDocs

- SC-491 - If there is an explicit link between the "Import1" node and the top-level diagram, there is a warning in the console

- SC-466 - Extra parameters in URL (like 'hide_navigator' or 'selection=wi-123') may be considered as change of ReqSet configuration

- SC-465 - Fix issues with models, which keep linking data internally

- SC-451 - If problems (e.g., network connectivity) problems occur during "Refresh" - it may lead to an empty ReqSet and loss of all the links to it

- SC-449 - If there was an error during initial import to a ReqSet, there is no possibility to overwrite broken ReqSet

Changes for Beta 2a

- Fixed regression where it was not possible to add a new project

- Improved handling of baselined or document revisions where links are maintained where possible

Changes for Beta 2

- Added a new Hide/Show Polarion pane action button to easily control the visibility of the Polarion navigation pane directly inside of Simulink

- Improved rich text support for imported Polarion requirements

- Added a new Polarion clean-up action button, to automatically remove deleted links or surrogate Work Items when changes have been made to the Simulink model

- Added a new Link Picker when using direct link mode. Note old mechanism is still supported

- Improved support for traceability and backlink processing, with Simulink System Composer

- Several bug fixes and improved compatibility

A possible way to work with Simulink is to parse the persisted model files.As a well known major problem with this approach is that the format of the serialized models might change over time(e.g. in 2012 suddenly the .slx format became default instead of the .mdl),causing extensive additional work to adapt to these changes for tools based on parsing serialized MATLAB file formats.For this reason, Massif uses the Java interface of a running MATLAB and discovers the model using Simulink modelspecific MATLAB commands.This way it is independent from the format of the files in which models are stored.However, it requires at least one running MATLAB instance to work.Currently, three MATLAB Connectors are supported:

Command Evaluation Server (in CE Server):it runs within the running MATLAB instance itself.To support this version, an additional server component (called MatlabServer) is needed to be downloadedfrom separate links provided for each version in the overview (details on how to set it up is discussed later).

If you would like to use the matlabengine connector from plain java application, please use themassif/maven/massif-matlabengine/.In this case, MATLABROOT must be set as an environmental variable pointing to your MATLAB root foldercontaining the /bin folder (for example: C:\Program Files\MATLAB\R2018b).

This allows connection to an already running MATLAB session.In order to do so, a MatlabServer has to be started from within MATLAB.After you downloaded thezipcontaining the MatlabServer, extract it to a folder on your computer, then make that folder as your current folder in MATLAB.

Edit the Java properties file named matlabserverconfig.properties with the serveraddress and serverport parameters.For example, set serveraddress = 127.0.0.1 and serverport = 1098. Run the setup_remote script.On the screen it will print the registered service name, which has to be entered on the preference page in Eclipse.If everything works well, you should get an output similar to the following:

Copy the service name into the 'Service name' field in the Simulink Preferences window.Execute addpath(%MASSIF_LOCATION%\git\massif\plugins\hu.bme.mit.massif.simulink.api\scripts')command in MATLAB to add scripts used by Massif to your MATLAB workspace.

Open the matlabserverconfig.properties file (next to the setup-remote script) and uncomment the debug = true line.If this property is set, the MATLAB console will print each executed command and you may be able to solve some issuesthat are hard to debug on the client side.

Another option is to use the open source MatlabControl Java APIfor communicating with MATLAB.This is integrated to Massif, the user can select this in Eclipse under the Window/PreferencesSimulink preferences page.

This connector handles MATLAB sessions itself.Currently it operates the following way: opens a new MATLAB instance at the first call and executes all the required commandsin this instance.

To use this connector you also have to execute theaddpath(%MASSIF_LOCATION%\git\massif\plugins\hu.bme.mit.massif.simulink.api\scripts')command to add MATLAB scripts used by Massif to your MATLAB workspace.

Connection or reconnection to a running MATLAB session is not supported with this connector.

Important: If you use additional libraries in Simulink, you will have to make sure themassif_functions.mscript is on the MATLAB search path when you are running the import(see issue #80 for details).

The MATLAB connector is no longer listed as an available option within Power BI. This change prompts the question of why it has been removed or is no longer accessible within the Power BI environment.

I want to use it MATLAB production server, which I'm currently not able to.

The usage is very user-friendly, as explained on UndocumentedMatlab.com (for example, case-insensitive parameter names with default values, different ways to specify start/end dates, etc.) Some usage examples are below.

3a8082e126