Jump to content
Sign in to follow this  
Crashphys

Detailed Multi-Domain Tutorial

Recommended Posts

Hi,

 

I am following the tutorial attached, but it is incredibly hard to follow and doesn't go into much detail. I was wondering if anyone has a more comprehensive tutorial for the multi domain method? Even the RADIOSS User Guide is vague on this topic. For example, both the User Guide and Tutorial say you need to use a type 4 link to connect the nodes of both domains together, however, I am eventually trying to do this with an SPH sub-domain and 2D shell elements, and need details. There are no details as to how these links are defined, as they are predetermined in the mono-domain beforehand. Furthermore, the files I end up with are fine_mesh_0000.rad and coarse_mesh_0000.rad. This is not the case in the file containing the complete multi-domain, which has two _0001.rad files and one _0000.rad file. Supposedly I am also supposed to making an input.rad, but it isn't clear how I can do this in a general case, and from what I can see in the pre-completed multi-domain analysis, this file should be generated automatically, but the instructions say to write it yourself. 

 

Can anyone please refer me to some very detailed instructions on the multi-domain method?

 

Thanks in advance.

RD - T - 3160 Multi-Domain Analysis Setup.pdf

Share this post


Link to post
Share on other sites

Hi,

 

check the following tutorials:

RD-E: 4500 Multi-Domain

RD-E: 2203 Ditching using Multi-Domain for SPH and ALE

 

This could also be helpful:

https://altairatc.com/europe/presentations/Session10/Session10_Altair_Wronski.pdf

https://altairatc.com/europe/Presentations_2009/Session_02/FORDRESEARCH_EHTC09_MultiDomainRadioss_Bach_Ford.pdf

Crashphys likes this

Share this post


Link to post
Share on other sites

Hyperman,

 

Following the instructions, I ended up with a .M00 file after exporting from Hypercrash, and no engine files. Can you help with this? The tutorial files have the starter and engine file for the multi domain, and only the engine file for the sub domain. I am only getting a starter file for both the multi domain and subdomain. I realise this is trivial, but I can't seem to find out how they managed to export the engine file. 

Share this post


Link to post
Share on other sites

I unchecked the option on the export panel and still ended up with the attached. I then tried it again with it checked, and got the same. 

coarse_mesh_0000.rad

fine_mesh_0000.M00

fine_mesh_0000.M00.bak

fine_mesh_0000.rad

fine_mesh_0000.rad.bak

coarse_mesh_0000.M00

 

I do not have the engine file merged in with my starter file as you do.

 

EDIT - SOLVED: I feel very stupid. So, for those with older versions of RADIOSS, the instructions I have followed work. Those with newer versions (I am using RADIOSS V14.0), all you have to do is follow the instructions on page 726 of the RADIOSS Tutorials and Examples Guide. Refer to the suggested reading from Hyperman. Thank you for the help Hyperman.

 

EDIT 2 - Since we're on the subject, I noticed that AMS and Multidomain are not compatible. I would like to understand why, so if anyone has any further readings on this topic, I'd appreciate it. I was also wondering how to determine which of the two is more effective. I realise AMS has the drawback of reduced accuracy, while Multidomain has none, and Multidomain only works effectively when there are a large number of elements in one domain vs another, but I was wondering if there was some other theory to compare the two methods.

 

Thanks for all the help!

Simon Križnik likes this

Share this post


Link to post
Share on other sites

I'm glad you figured it out.

 

I do not know why AMS and Multidomain are incompatible, but you can use conventional mass scaling (DT/NODA/CST). Actually, timestep difference is the critical factor for effectivness of Multidomain technique, because the smallest time step determines the performance of the (sub)model. In general, AMS is effective where timestep is homogenous, while Multidomain is the best choice for models with local mesh refinements.

Crashphys likes this

Share this post


Link to post
Share on other sites

I see. Thank you for the clarification. I suppose I will have to rely on AMS, as it looks like Multi-Domain won't work for my application.

 

Just to add some further documentation for future viewers: I actually ended up looking deeper into the theory manual as well, and it seems unfortunately for my application it will not work. Turns out for multi-domain, it's also important you have a very small amount of contact surfaces that are well defined, so it's not great for the application of fluid sloshing in tanks, but works great if you have an example like ditching, where it will be a simple and direct interface between the two domains.

 

Thank you very much for your help Hyperman.

Simon Križnik likes this

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
You are posting as a guest. If you have an account, please sign in.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...