![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: How to Handle Deleted Baselines Topic Summary: DXL Script Choking on Deleted baselines Created On: 7-Jan-2008 16:47 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I have a script that loops through baselines. One of my more important
documents has two deleted baselines. Is there any way to check to see if a baseline has been deleted? (Isbaseline, baseline Exists do not work for this.) Barring that, can baselines be purged? (Please know that another company is handling our DOORS admin which is why I'm kind of stuck,) THanks, Tara ------------------------- Tara L. Wilk Curmudgeon-at-large, NGC engineer in spare time |
|
![]() |
|
![]() |
|
Good question.
I'm using DOORS 8.1 and when I run the attached script it doesn't even see the deleted baseline (Baseline 26.0) or it just skips over it. ...... Baseline: 24.2 Baseline: 25.0 Baseline: 25.1 Baseline: 26.1 I'm pretty sure you can't purge a deleted baseline, as once it's deleted it can not be recovered, so in a sense when you delete it you purge it. In 8.1, it only makes an entry in the view baselines dialog that a baseline was deleted. ------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com Edited: 7-Jan-2008 at 17:00 by Scott Boisvert |
|
![]() |
|
![]() |
|
Unlike modules and objects which have an invisible deleted state different than the purged state, Baselines (and also attrs) either exist or not. Deleted baselines are gone.
As far as I know there is no way to detect it for sure, but you could infer that a baseline was gone by plowing through History [1] there would be gaps in histor [2] some attributes will magically have changed values between baselines even though there is no History to record the change [3] a deleted non-suffixed baseline should be detectable since its number is missing; that is if baseline 1.1 and 1.3 exist, you can infer 1.2 was deleted; but if 1.1 and 1.2b exist, its not certain that there were any in between. None of these methods are 100% deterministic, however. - Louie |
|
![]() |
|
![]() |
|
Another question I should probably ask, is if it is really choking on the deleted baseline or if it's choking on a corrupted baseline.
I've had issues with scripts and corrupted baselines, but never deleted ones. For some reason I was able to get around the issue by putting the baselines in an array first, then looping through them to get the info that I needed. Not sure how I stumbled onto the solution, but I had been working for about 20 hours straight.......The mind was wandering into places I would rather not talk about from lack of sleep.... ------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
|
![]() |
|
The deleted baseline may be a red herring.
If you are doing stuff with the baseline within a baseline loop then you are asking for trouble. Don't know why - that's just the way it is. You must instead loop through baselines and store handles in a skip and then access them outside of the loop. I'll see if I can find the thead where Louie explains his experiences with this issue. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
Yes I had this years ago. Turns out my outer "for bl in mod do" loop had a nested "for bl in mod do" loop burried in one of the library routines. DOORS doesn't seem to like that at all and the inner loop was messing up the outer loop. Seems to do the same thing if you have nested "for lnk in obj" loops as well.
Yes, the standard method for these things is to insert them into a skip list and THEN deal with them, something like attached. Take note of the 'Sequencer' that insures the baselines are retrived in the original order detected. - Louie Be advised that this doesn't work for 'History' types, since making an assignment with a History variable does NOT copy the value, it makes an alias. You cannot therefore plow through History keeping track of the last History that modified Object Text; instead you would plow through counting History, keeping track that perhaps #34 was the last one, then plow through History again until you came to #34. |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
How to Handle Deleted Baselines
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.