Learning Forum

[info]

Hello,

While working on a mechanical probel, I experienced weird behaviour in ANSYS Discovery AIM, I'd like to address these.

Issue #1: AIM user interface starts to responds very slowly (click/apply) when several mesh controls actively defined.

Issue #2: Parallel to issue #1, I can no longer open my ongoing, properly saved projects.

Issue #3: Archive file size is huge although there is only Mesh definition exist in the project (no Physics, either Results branch defined).

More details.

Issue #1

After a decent number of misc. mesh controls applied in the project, e.g. size controls, element type and boundary layers roughly 10-12 in total). While try to apply new controls, the reaction of the application gets very-very slow. First I thought for some misterious reasons I incidentally ran out of memory or so (see end of e-mail, with my WS configuration), so I properly saved my project and exit AIM.

Issue #2

After restarting and while tried to open my just previously defined project, AIM starts to open it, but at 78-89% of the opening progress, it stops and then exit the program. Doesn't matter how many times I tried to re-open it, it behaves the same. Naturally while I was performing the definitions I didn't make any backup archived copies of my work, so I lost everything.

At that point I decided to redo everything and started over. Although I started to define the mesh controls in a differennt order, when reaching roughly the same number of controls in AIM, it again started to reproduce issue #1.

During this second run, I thought I was being smarter and regularly kept archiving after a new plate got all intented mesh controls (2-3, size, shape, infl.). See also the number of archives I created on the attached screenshot. This didn't help me either. After experiencing Issue #1 again, then I properly exit again and start to open (1st) my last archive: no success! 

I can only successfully open my 2nd ('TESTRIG_rev0_iter202.wbpz') archive, from the 3rd one it is inpossible.

Issue #3

Please take a look at the archived file sizes this above procedure created. I think it is huge, especially considering there is only the following branches created in the project: Geometry, Model Configuration, Mesh.

At my company, I regularly uses ANSYS Workbench Mechanical, most of the times there are 10-15 Static Structural branch is defined in the Project Schemtaics and never experienced such file sizes without results included.

My WS is equipped w/ 128GB RAM, RAID0 500GB SSD and dual XEON E5 w/ 20 physical cores.

Since there is a size milit for the attachments here (which I also think that doesn't make sense), please find all the archived files here:

 

Please help me how to solve these problems. 

Regards,

Csaba

[Naresh Patre]

Hello steelxpert

Can you let me know the additional mesh controls that you added after saving file TESTRIG_rev0_iter202.wbpz? I would like to repeat them to see if any particular setting is causing this crash.

Meanwhile I will also discuss this issue with development and see if the project can be restored.

[info]

Hello Naresh Patre

Unfortunately I cannot tell you that. There shoul be a dozen and please also consider that there were 2 rounds (I started over the whole process) and during the second attempt I tried to proceed on different plates.

[Naresh Patre]

Hello steelxpert

I think the crashing problem is arising due to the presence of "Configuration" task between Geometry and Mesh. Using project  TESTRIG_rev0_iter202.wbpz when I added any element shape or sizing, then saved the file, reopening the project led to crash. This is what you also observed. So I deleted the Configuration task, then connected the Geometry task to Mesh task and regenerated the mesh. Then I added Element shape and Body sizing, meshed the model, saved it and reopened it without any crash. I am sending you this modified model for your reference through a secure transfer link via email. Can you please check it out at your end and let me know if you encounter any crashing issue upon adding new mesh controls and sizes?

[info]

Hello Naresh Patre

Thank you for the hint.

The provided links doesn’t work, I got this in the browser: ’ The service is unavailable.’

Regards,

Csaba

[info]

Hi Naresh Patre

Thank you for the link. Since the system was down and I needed to progress, I ended up starting over the whole process again. But this time I kept documenting the whole process.

Issue #1

I followed your instruction and avoided the 'model configuration' task this time. Up to the point I get in this loop, I haven't experienced the issue explained above. Can you also comment it whether it is an issue that will be fixed?

Issue #2

Unfortunately, this happens again, please check the log file I created: it is the last iteration ('TESTRIG_rev1_iter008.wbpz') when this issue started. As for now, it seems that AIM 'doesn't like' to deal with several 'Element shape' controls...

Issue #3

Can you also comment it: is it normal to have such a huge file sizes with mostly only geometry and some mesh definitions?

Please find the new archives at:

Thanks,

Csaba

[Naresh Patre]

Hello steelxpert

Issue #1: I will submit a defect for this issue related to Configuration task.

Issue #2: I was able to reproduce the issue in file TESTRIG_rev1_iter008 where the Mesh control and sizing definitions are taking a couple of minutes. I will also submit a bug for this issue. 

Under file TESTRIG_rev1_iter007, you have mentioned that "And this is the point where ’issue #2~ reappeared again" on page 10 of the doc. Do you mean that AIM crashes at this stage? I was not able to reproduce it with the given file.

Issue #3: I am looking inot the file size issue and will update you.

[info]

Hello Naresh Patre

Thank you for your feedback.

At the reappereance of Issue#2 I meant the slow repsonse time.

[info]

Hello Naresh Patre

Can you give me an update, most importantly on Issue#2?

Thanks,

Csaba

[Naresh Patre]

Hello steelxpert

I have submitted following defects for the 3 issues reported:

250793 - Discovery AIM crashes after adding mesh control

252537 - AIM - It takes ~ 3 min. to add mesh control

253569 - Discovery AIM - File size increasing

I will update you as I hear from the development team about the progress of these defects.

[info]

Hello Naresh Patre

Thank you for the feedback.

[info]

Hello Naresh Patre

Please update me on the status of the reported issues and send me an official statement from ANSYS developers when these will be bug-fixed?

What I am most concerned about are the #250793 & #252537 reported issues. Without these fixed one cannot use the software for qualitative mechanical results, which I believe should be a main purpose of AIM.

I need to know these answers since my subscription period will end this month and my license gets perpetual, that means that I will lost the chance to get the (new) release which will contain the solution to these.

If that unfortunate event happens I need to file an official complaint via local ANSYS representatives, because then it gets obvious that AIM has been advertised and sold for tasks it is not capable of.

Thank you for your help.

[Naresh Patre]

Hello steelxpert

I am seeking update from development team about these defects and will let you know their response.

[Naresh Patre]

Hello steelxpert

The bug 250793 is no longer reproducable in 2020 R2 version. 

Regarding bug 252537, it's still being investigated and will let you know once it gets fixed.

Though I haven't seen these mesh control related issues (crashing and slowing the process) reported by other users, I will take one of the complex models posted in application examples and try to see if the issues can be reproduced. I think these could be mostly model specific issues. I am also checking with the development team if these issues were already reported (again I don't think so because the bugs that were submitted were not marked as duplicate, indicating that these might not have been encountered with other models). I will keep you posted.