Close All | Open All
Yes.
No. medini unite starts an own instance of Matlab for the compare and merge activities.
Please use the medini diff tree for model navigation.
You should not do it. medini unite keeps an undo/redo stack and changing the models outside the control of medini unite may lead to unwanted model changes.
To be able to analyze very large models, medini unite is configured by default to use up to 1GB of memory. If your computer has less than that available, medini unite might not start at all. To decrease the amount of memory required by medini unite, please open its configuration file, usually located at: "C:\Program Files\ikv++ technologies ag\mediniUnite\mediniUnite.ini". Change the line "-Xmx1024M" to something smaller, e.g. "-Xmx512M".
Please invoke matlab.exe /regserver from the command line in your matlab installation directory. There is a Mathworks problem with the used Ids of their COM servers so some versions have identical Ids and cannot be distinguished.
There is a refresh button on the right top of the diagram frame that can be pressed to re-catch the Simulink-windows.
medini unite has been tested with ClearCase v7.1, but older versions should work as well.
Yes, medini unite offers a command line interface which can be integrated with most SCM systems. It has been tested for SVN and ClearCase but reported to work with others, too.
You can configure the property filter from the preferences menu.
medini unite offers filter functionality on the property level. You can exclude a number of properties form the difference analysis. A predefined set of properties is available for graphical properties (position, colouring etc.)
Yes, medini unite detects all installed MATLAB versions form the registry and presents the detected versions to the user for selection.
Yes, you may load the model with a newer version of MATLAB (from 2006a), do the diff/merge with this newer version and save the model again in the older MATLAB version.
Yes, it contains all merge actions that have changed the target (left) model.
Yes, it contains all element, line and property differences. Furthermore, the pictures of the diagrams are contained in the report. The report uses the same colouring schema and symbols as the medini unite diff tree.
A difference report and a merge report are available.
At startup, medini unite starts the Matlab COM server in order to visualize differences in Matlab from the beginning. That takes a constant time at startup. One way of improving performance is to prevent medini unite form colouring differences on the diagrams. You can do that from the preferences window.
medini unite uses the elements name and its position to detect what elements have the same identity and need to be compared. If the name has changed, but the position remains, medini unite will detect the name change automatically. For other situations, in case you want to enforce that two elements of the same element kind are to be treated as having the same identity, you may use the ?unite? functionality. After applying ?unite?, the content of the subsystems will be analyzed.
Referenced blocks will be compared by content, if the user requests it. In that case, medini unite will open a separate difference analysis window for the models (libraries) containing the referenced blocks
medini unite finds all differences between the compared models and visualizes them in the tree view, on the diagram and in the property view. If a difference is not shown, it might be that filters have been configured in a way that prevents the difference to appear.
Yes, medini unite offers an automatic merge from the source (right) to the target (left) model. This auto-merge functionality can be invoked on all containers in the tree view and works recursively on the content.
Yes, medini unite offers a multiple Undo/Redo functionality. In case of the very rare exceptions, medini unite warns that a certain decision cannot be undone.
medini unite is well tested with model files in English, Japanese and German language. The localization of the tool user interface is currently available for English and Japanese.
Yes, medini unite can handle source and target files of different MATLAB/Simulink versions if the models have been created with a Simulink version that is not newer than the one installed. medini unite offers the possibility to convert older models to the Simulink version installed, but can also leave the models in their original version.
medini unite has been developed for and tested against all 32-bit and 64-bit versions of MATLAB/Simulink starting from 2006a. Some users reported that they could work with medini unite also on earlier versions of MATLAB/Simulink, but those haven't been tested much by ikv. If you have a specific request, please let us know
medini unite currently supports Microsoft Windows OS (2000/XP/VISTA/Windows-7, 32-bit and 64-bit). However, as medini unite is based on eclipse it has only a limited dependency on Windows, mainly for visualizing the Simulink model inside the medini unite application and for certain invocations of the MATLAB/Simulink COM API. Therefore we will consider the platform independent MATLAB/Simulink API and plan to provide a UNIX/LINUX version of the medini unite.