Integrity Check

[Thomas Mercer-Hursh]

I am writing some code to load models into a repository directly ... a bit exciting given the lack of documentation about the data structure.  Having proceeded to the point where I have a model I can open, one of the first things I was inclined to do was to run the Project Integrity Check to see whether the model was correct or, if not, what was wrong with it.

My first problem is that the check seems not to run to completion.  I started with all the defaults, but now have tried doing them one at a time, starting with Package Structure.  The progress bar goes across at a reasonable pace ... considering that the model file is now over 200MB ... and gets about 85% of the way and then just stops.

The second problem is that it is a bit "terse" about what it finds.  E.g., on the Package Check it has listed two issues as Invalid Package Object, but it says nothing about what is wrong with that object.  Is there somewhere that one can get a wee bit more detail?

[«Midnight»]

I ran into something like this recently, with build 818 though. I put it down to a hiccup, then never came back since we repaired the model another way.

Perhaps there is a bug in the check; it shouldn't fail silently, and I don't remember it doing this in the past.

David

[Thomas Mercer-Hursh]

Lucky me ... I'm running 818.

[«Midnight»]

Have you tried it on the 7.1 beta? You could see if the problem(s) persist, then log those that do (since you'd have more than one build with the issue).

You can always reinstall 818 - I'd advise using the full kit - after you did the trial.

Just to be safe I'd also suggest only working on copies of your models to check this. Don't open any 'real' models until you revert back to 818.

David

[Thomas Mercer-Hursh]

No, I haven't tried it on 7.1 ... I would be happier about doing that if I could have both installed at the same time since I could easily use 7.1 only for the new experimental model.

[«Midnight»]

Yeah, been there...

[KP]

No, I haven't tried it on 7.1 ... I would be happier about doing that if I could have both installed at the same time since I could easily use 7.1 only for the new experimental model.

You could rename EA.exe to EA818.exe (or similar) before installing 7.1.

[«Midnight»]

Or just copy the entire directory tree and change back afterwards.

Neil: I'm assuming without proof that the registry trees are compatible. Is this so?

[Thomas Mercer-Hursh]

Registry is the question, I think.  I can happily and easily install 7.1 in a different base directory ... I tend to do that anyway.

[«Midnight»]

Let's wait [EDIT: a bit] to see if Sparx will shed the necessary light.

[Thomas Mercer-Hursh]

Doesn't seem to be leaping to the fore ...

I don't suppose there is another version of the Integrity Check, somewhere as a separate tool?  The built-in one seems to be aimed more at checking on and repairing small bits of damage, e.g., something that might have resulted from a bad write or something.  I.e., it is best at identifying individual small errors and fixing them.  What I could use would be something that gave a more thorough report on what was wrong.

E.g., I had one message which identified that there were 12970 instances of child package ID does not match parent.  By doing a few queries I was able to identify that there were 12970 combined t_object references to three stereotypes, each of which is one flavor of subcomponent, so it became pretty clear with a little looking that I was failing to set the parent ID correctly in this class of object.  I haven't run the fixed code yet, but I feel like I know where the issue is pretty clearly.

Now I have a bunch of reports that just tells me Invalid connector, but doesn't tell me anything about what is invalid about it.