-
-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The exported model doesn't contain all nodes #653
Comments
@eoursel let me inform you that I have created a new more general issue to fix reported by your one. It is not only a problem with DI. The problem must be investigated using dedicated Unit Tests but not the whole model. I will get back to the reported issue after fixing this. |
- added ModelFactoryUnitTest tests against children
- Working on a fix - work in progress - UT 👍
work in progress - unimportant changes.
Hi @mpostol Sorry for the late answer. i am aware that the DI is just an example. I took the DI because this is one of the model where OPC Foundation publishes the NodeSet format and the ModelDesign format. Most of the new companion specifications do not contain the ModelDesign format. I am currently interested by the IEC61850 companion specification more than the DI. If you have already done the translation to ModelDesign for IEC61850 let me know. Nice weekend. |
Hi @eoursel. We are still working on recovering ModelDesign for all available models using the current version of the asp. Check out the folders ModelDesign added to all models in the repository mpostol/UA-Nodeset. Models have been generated thanks to @mertyusaatag contribution. He is working on an independent fork: The final results are proposed by him as pr to my repository. I have just checked that the model you requested is not created for some reason😒. I have notified @mertyusaatag by adding a comment to the appropriate issue.: mertyusaatag/UA-Nodeset#11. It was already closed so the problem needs investigation. He promised to investigate the problem in detail next week. BTW let me stress that the current version of the asp ( |
ModellingRule
|
Describe the bug
Not all nodes are recognized following references starting from the selected to export nodes. Some nodes are not members of the complex types. Additionally, some nodes may be duplicated if they are targeted by many references.
To Reproduce
Analyze the result of
UAObjectTypeTestMethod
and recover the DI modelTasks
AllNodesInConcern
AllNodesInConcern
AddNodeFactory
is used or there is a key conflictAdditional context
It contributes to:
The text was updated successfully, but these errors were encountered: