Unload a loaded baseline

I'm trying to collect all the history records of an object across baselines using the solution of Galactic Solutions Group (http://www.galactic-solutions.com/GalacticDownloads.htm)
For a big module with lots of baselines, Doors fills up the system memory and stops. I think the problem is here:

for b in baselines do {
baselineModule = load( b, false )
if ( !null baselineModule ) {
HB_populateHistoryListBox( HB_historyListViewDBE, baselineModule, o, b, historyRecordCount )
}
}

Is there a way to unload the loaded baseline from the memory?
I tried the unload() and close() command, but neither works.

Can someone help me?

Thanx,

Gabor
GaborMoizes - Tue Oct 26 07:40:56 EDT 2010

Re: Unload a loaded baseline
Mathias Mamsch - Tue Oct 26 08:07:00 EDT 2010

Closing the baselines should work by the way, i.e. should release the memory for the baseline module in memory. If system memory gets filled up anyway, then this is maybe a bug in the smart history viewer script not releasing its memory properly.

I think you should take the time and modify the script, so that the data of the baselines is loaded on demand, meaning you should add another listbox to the left side of the history records box and list all the baseline there with checkboxes. When a user selects one of the baselines the script will load the baseline and update the contents of the history records including the baseline. Otherwise the baseline will be skipped when displaying the history records. Deselecting an item should close the baseline.

If you come around doing that (I think it should not make a very big change) it would be great if you shared the result to the community. If you need help, we are glad to assist you.

Regards, Mathias

Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

Re: Unload a loaded baseline
GaborMoizes - Wed Oct 27 03:39:56 EDT 2010

Mathias Mamsch - Tue Oct 26 08:07:00 EDT 2010
Closing the baselines should work by the way, i.e. should release the memory for the baseline module in memory. If system memory gets filled up anyway, then this is maybe a bug in the smart history viewer script not releasing its memory properly.

I think you should take the time and modify the script, so that the data of the baselines is loaded on demand, meaning you should add another listbox to the left side of the history records box and list all the baseline there with checkboxes. When a user selects one of the baselines the script will load the baseline and update the contents of the history records including the baseline. Otherwise the baseline will be skipped when displaying the history records. Deselecting an item should close the baseline.

If you come around doing that (I think it should not make a very big change) it would be great if you shared the result to the community. If you need help, we are glad to assist you.

Regards, Mathias


Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

Maybe I'll modify it, but which command closes the loaded baseline? If I could close it at the end of the loop, I think the problem would be solved.

Regards,

Gabor

> Mathias Mamsch wrote:
> Closing the baselines should work by the way, i.e. should release the memory for the baseline module in memory. If system memory gets filled up anyway, then this is maybe a bug in the smart history viewer script not releasing its memory properly

Re: Unload a loaded baseline
Mathias Mamsch - Wed Oct 27 08:58:34 EDT 2010

GaborMoizes - Wed Oct 27 03:39:56 EDT 2010
Maybe I'll modify it, but which command closes the loaded baseline? If I could close it at the end of the loop, I think the problem would be solved.

Regards,

Gabor

> Mathias Mamsch wrote:
> Closing the baselines should work by the way, i.e. should release the memory for the baseline module in memory. If system memory gets filled up anyway, then this is maybe a bug in the smart history viewer script not releasing its memory properly

You need to do "close baselineModule" just like you close any other module. You should do it inside of the loop when you don't need the baselinedata anymore, but still it will take forever to get information about one object, because each time all the baselines will be opened and closed.

I just wondered, since you said you tried close and it did not work.
 

for b in baselines do {
    baselineModule = load( b, false )
    if ( !null baselineModule ) {
        HB_populateHistoryListBox( HB_historyListViewDBE, baselineModule, o, b, historyRecordCount )
        close baselineModule       
    }
}

 


Regards, Mathias

 

 


Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

 

Re: Unload a loaded baseline
GaborMoizes - Thu Oct 28 07:41:24 EDT 2010

Mathias Mamsch - Wed Oct 27 08:58:34 EDT 2010

You need to do "close baselineModule" just like you close any other module. You should do it inside of the loop when you don't need the baselinedata anymore, but still it will take forever to get information about one object, because each time all the baselines will be opened and closed.

I just wondered, since you said you tried close and it did not work.
 

for b in baselines do {
    baselineModule = load( b, false )
    if ( !null baselineModule ) {
        HB_populateHistoryListBox( HB_historyListViewDBE, baselineModule, o, b, historyRecordCount )
        close baselineModule       
    }
}

 


Regards, Mathias

 

 


Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

 

OK, I've modified the Smart History Viewer. Now it works better for large modules and/or numerous beselines.

Modifications:
  • Added closing of each baseline after processing to avoid out of memory error.
  • Added progress bar to show the progress of processing

Enjoy it! :)
Attachments

attachment_14547322_smartHistoryViewer.dxl

Re: Unload a loaded baseline
GaborMoizes - Thu Oct 28 07:45:11 EDT 2010

GaborMoizes - Thu Oct 28 07:41:24 EDT 2010
OK, I've modified the Smart History Viewer. Now it works better for large modules and/or numerous beselines.

Modifications:

  • Added closing of each baseline after processing to avoid out of memory error.
  • Added progress bar to show the progress of processing

Enjoy it! :)

Sorry, I've attached the wrong file.

It is not about the Smart History Viewer, but the Galactic Solutions's Group History Viewer. :)

Find attached the right file.
Attachments

attachment_14547323_ojectHistory.dxl