Rendering Error

[Ali Ozdemir]

Following project was compiled couple of days ago but now it doesn't compile.

https://openbrim.org/objido1uc20xutpjiogbi28mafbrmv4.project

[Ali Koc]

It is trying to compute sectional properties for 185 sections. If you wait a minute or so, it should open up. It seems most of these sections are the same so we should be able to make this process much faster.

[Ali Ozdemir]

Even if we come up with some optimization for similar sections, it will take good amount of time to calculate it. For my case I don't need to calculate sectional properties for every compile. I need that when I do finite element analysis.If we can create a function for section properties calculation, it can be much more better.

[Ali Koc]

Starting v3.160604, pushed the sectional properties calculation process into its own thread. That means it will work independent of the compilation step and should not slow things down as nothing waits for these calculations to complete.

However, if you do need to access sectional properties from within your application, you need to wait for SectionPropCalcComplete event.

[Ali Ozdemir]

I tried but I cannot read the shape parameters after SectionPropCalcComplete event from API. It only shows these properties in browser.

[Ali Koc]

Try OBrIM v3.160605 from this link:

https://goo.gl/RCOFvn

Make sure that after receiving SectionPropCalcComplete event, you use ObjectGet method of OBrIMConn object to get the updated object data.

Let us know how it goes.

[Ali Ozdemir]

Thanks, it is working now but computer freezes when it tries to do calculation. Between SectionPropCalcStart - SectionPropCalcComplete events. I couldn't see similar freezing problem when I don't use API.

If there is a way to solve this freezing problem for API, this solution will work for me. Otherwise I have 2 comments about the issue:

-Why do we need section properties for every compile? Why don't we just compute it before code check or finite element analysis?

-If we have to compute it for every compile then I think it is unnecessary to compute section properties for every section - for every compile. We may consider only computing section properties when the object parameter changed or object is added. Does that make sense? - or is it something that can create problem when we use alignment?

[Ali Ozdemir]

when I change the multithreading to true from settings.ini file , it solved the problem.

mt=1 # multithreading support for OpenBrIM UI