sticky rmi integration errors

Question

Robert Lummert 2019-3-29

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/453238-sticky-rmi-integration-errors

评论： Robert Lummert 2019-4-26

We once tested the Intland Codebeamer requirements integration to Matlab/Simulink. Later we decided to use other tools for requirements management. With the Matlab-Release we installled it to there are no problems, but on more recent release installations we get warnings and errors like

Warning: Failed to register requirement link type "intland_codebeamer_rmi".

Error message: Undefined variable "linktypes" or class

"linktypes.intland_codebeamer_rmi".

Warning: Failed to resolve link type by registration name:

intland_codebeamer_rmi

> In rmiml.selectionLink

even though the integration has never been installed there. Any suggestion how to get rid of it?

4 个评论
显示 2更早的评论隐藏 2更早的评论

Artem 2019-4-23

previous registration for custom document type is stored in user preference under your prefdir.

Usually you get a new prefdir when you install a newer version of MATLAB, but if your previous settings where copied, you will get the old registration.

To cleanup all custom document type registrations in your user preferences, run the following command in MATLAB:

>> rmi.linktype_mgr('reset')

Robert Lummert 2019-4-24

Hi Artem,

thanks for the answer. Actually I was asked by Mathworks staff (Joshua) to remove the prefdir for 2019a already, but this didn't help. Accidentally I just now ran rmi.linktype_mgr('reset') on R2018b (where - magically - the warnings never occurred, anyway). When I opened R2019a the warnings were already gone. Does this mean R2018b installs with a virgin set of preferences, while 2019a installs with a copy of some patchwork of older installations' preferences without asking me? And does running rmi.linktype_mgr('reset') on one installation modify ALL installations?

Best regs,

Robert

请先登录，再进行评论。

请先登录，再回答此问题。

Answer 1

Robert Lummert 2019-4-26

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/453238-sticky-rmi-integration-errors#answer_372389

As it seems

>> rmi.linktype_mgr('reset')

will solve the problems (thanks again to Artem, see comment above).

But one should be careful when having multiple Matlab installations on the same machine (e.g. when doing toolchain engineering), as this command seems to influence not only the Matlab installation it is executed in.

2 个评论
显示无隐藏无

Artem 2019-4-26

This is true in general: All user settings accessed via Requirementns > Settings dialog, or via rmipref() API are stored in rmi_settings.mat file under user's prefdir. If you are experimenting with mutiple installations of MATLAB and reusing the same prefdir content, you will notice that settings you change in one installation will show up when running the other installation. May be the workaround is to use different usernames (tester1, tester2, ... that sort of thing).

Robert Lummert 2019-4-26

If your job is to maintain model based toolchains using simulink, you need to have different versions of matlab installations available, I wouldn't call this experimenting.

The different user approach then has major drawbacks as many network resources (net shares, email, different company portals) won't be available like that. And even worse: I would need as many sets of licenses as users, or I would have to switch all licenses to machine licensing, meaning they can't be swapped with other users anymore.

For many years parallel installations of Matlab were care free, but now it seems to become a real pain in the ass. Is there any reason for messing up the preferences of different installations where it comes to rmi? I mean, you still have seperate sets of preferences in the roaming data folder and some other settings still seem to be handles independently...

请先登录，再进行评论。