Feature #1307
open
Supply several model databases
Added by Pavel Shved about 13 years ago.
Updated about 13 years ago.
Description
Instead of specifying one model database, why wouldn't we allow user to specify several? This way, a user could run models both from the "default" file shipped with ldv-tools, and from his or her own one he or she keeps in his or her home folder named after him or her.
As far as I understand, it would require fixing Rule Instrumentor only.
Don't you like LDV_KERNEL_RULES option? That environment variable allows to specify any directory containing models. The only restriction is that it should contain model-db.xml file in correspondence with default naming scheme. But the rest part of that directory and even model-db.xml can be completely user defined (except they have to have right readable format).
As for me I have used this option in developing 43-1a model to avoid continuous submodule pushing and updating.
I like LDV_KERNEL_RULES very much also :)
Eugene Novikov wrote:
Don't you like LDV_KERNEL_RULES option? That environment variable allows to specify any directory containing models.
Ok, but can it specify several model-db.xml-s, so that a model is searched in all of them? I bet it can't. While current solution fulfills your needs as those of a developer, the needs of a user easily go beyond testing a specific model. Take Alexey as an example: he has to merge his RCU_1 custom model into model-db.xml at each its update. That's not the best user experience we can provide.
Pavel Shved wrote:
Take Alexey as an example: he has to merge his RCU_1 custom model into model-db.xml at each its update.
Alexey, I completely forgot to ask you: please add your rule about RCU in our rule database!
Also available in: Atom
PDF