Multiple unconnected stl files
I'm new to snappyhexmesh, I have 5 unconnected regions in 5 files. 2 rotors, 2 AMI, 1 outer cylinder. I used the propeller snappyhexmeshdict to try to mesh my stl files. Do I need to create all the meshes separately? Or can I mesh the 5 region as 1 system, even though they are not connected?
|
It is not exactly clear what you are looking for--more info please. Pictures may be helpful. When you say 'unconnected region' what exactly do you mean? If you are saying that you have each surface or patch defined in its own file as a separate body then you may be able to just concatenate the files into one stl. That said, snappy requires a closed stl so you need to be careful that the original stl is good quality.
Again, more info gets you better help. Less info, and only few people are willing to take a wild stab in the dark... |
1 Attachment(s)
Thank you for your reply. By unconnected I mean the patches share no faces. When I run my snappyhexmesh, the only part that is shown is the lower AMI. The blockMesh background doesn't change at all. Here is my snappyhexmeshdict and a pic of the lower AMI. My stl files are closed and I'm not getting any error messages from my snappyhexmesh log file. Any ideas of where I'm going wrong?
HTML Code:
/*--------------------------------*- C++ -*----------------------------------*\ |
Quote:
What you want to do is combine all of these into a single closed stl. You can just concatenate them and give each "solid" the name of the patch in the stl file for each solid part. As in: ... solid rotor1 <facet stuff> endsolid rotor1 solid rotor2 <facet stuff> endsolid rotor2 ... Perhaps you have already named these in each individual stl? Just take a look at the first line--it will read "solid <name>". After you have a combined stl file--let's call it "full.stl"--then you read in just that one stl file into snappy as but then have separate 'region' full.stl { type triSurfaceMesh; name full; regions { cylinder { name cylinder; } rotor1 { name rotor1; } ...[repeat for all patches]... } } The reason you have to add the region defs and names for each patch is because as a default it will name each as full_rotor1, full_rotor2, etc. You could just change this in you polyMesh/boundary file after it is created, but this saves a step later on. As an alternative you could keep the full.stl unamed and then make your patches later on by running surfaceToPatch using your individual stl files. Based on the still somewhat sketchy information you have given about what your geometry actually looks like this is my best guess. Hope this makes sense and is helpful. |
Thank you for your help. You answered my question, I didn't mean to be so vague. I just commented out all but one surface, then added 1 new surface when the previous surface was visually correct.
|
Follow-up question to this old post
Hey all,
Lurker and new to posting. I had a question about this case and was wondering if anyone may be able to help. It was advised to merge all stl files into one and then name the separate regions in the snappyhexmeshdict, but how does the dict know which solids you're referring to in the stl file? Say for example, I have 4 different solids combined in one stl file. How does the dict know which of the 4 I'm referring to when I create the definitions? Are there names for the solids attached somewhere in the stl file? Thank you |
Given you have an ASCII STL, try opening it up with a text editor ;)
If its binary, you can try to open it in Paraview and save as ASCII, I am not sure if it carries over the names correctly, though. |
All times are GMT -4. The time now is 17:09. |