I am trying to get contour plots of stress for my 3D SG using the Abaqus-SwiftComp GUI but it seems I am getting all kinds of errors, like the one below.
You can try this: Read Local States - sgio 0.2.10 documentation
This guide is for 2D cross-sections with VABS. You can follow the guide first to see if it can be applied to the 3D SG with SwiftComp.
@su.tian.22 Could you share an example with 3D SG dehomogenization using sgio? I followed the instructions but it looks like it cannot read sc file.
I also got this error during dehomogenization
SwiftComp begins at 171647.655
Inputs echoed in file wing3dSG_archive.sc.ech!
Constitutive modeling for a 1D (beam) model!
Dehomogenization will be carried out!
You are running SwiftComp with full integration!
Finished reading/processing model file!
Local fields can be found in file wing3dSG_archive.sc.u and wing3dSG_archive.sc.sg and wing3dSG_archive.sc.sn!
Local fields in material coordinates can be found in wing3dSG_archive.sc.snm and wing3dSG_archive.sc.sgm!
I/O error: Global variable in stress/strain
What does I/O error: Global variable in stress/strain mean?
Can you send me some files for testing?
Also, what are you going to do with sgio?
In which step do you need sgio?
Below is simple example (added .txt extension):
spar3d.sc.txt (101.7 KB)
What I have done is:
Using K file from swiftcomp output to run analysis using GEBT, which generates output file for the macroscopic beam.
What I want to do is:
I think I need both steps?
Please read SwiftComp manual to understand what you are doing. Try to link what you are trying to do in the corresponding equations of your theory. If you know the theory, they you can understand the error and correct your inputs.
@su.tian.22
I used a quadratic mesh containing wedge15 elements but it seems that sgio does not recognize this element type.
Traceback (most recent call last):
File "<frozen runpy>", line 198, in _run_module_as_main
File "<frozen runpy>", line 88, in _run_code
File "D:\Users\liu3856\AppData\Local\Programs\Python\Python311\Lib\site-packages\sgio\__main__.py", line 6, in <module>
cli(*sys.argv)
File "D:\Users\liu3856\AppData\Local\Programs\Python\Python311\Lib\site-packages\sgio\app.py", line 119, in cli
main(func, **vars(pargs))
File "D:\Users\liu3856\AppData\Local\Programs\Python\Python311\Lib\site-packages\sgio\app.py", line 139, in main
convert(
File "D:\Users\liu3856\AppData\Local\Programs\Python\Python311\Lib\site-packages\sgio\iofunc\main.py", line 682, in convert
sg = read(
^^^^^
File "D:\Users\liu3856\AppData\Local\Programs\Python\Python311\Lib\site-packages\sgio\iofunc\main.py", line 84, in read
sg = _abaqus.read(
^^^^^^^^^^^^^
File "D:\Users\liu3856\AppData\Local\Programs\Python\Python311\Lib\site-packages\sgio\iofunc\abaqus\_abaqus.py", line 88, in read
mesh, materials, mocombos = process_mesh(inprw)
^^^^^^^^^^^^^^^^^^^
File "D:\Users\liu3856\AppData\Local\Programs\Python\Python311\Lib\site-packages\sgio\iofunc\abaqus\_abaqus.py", line 451, in process_mesh
mesh = Mesh(
^^^^^
File "D:\Users\liu3856\AppData\Local\Programs\Python\Python311\Lib\site-packages\meshio\_mesh.py", line 146, in __init__
cell_block = CellBlock(
^^^^^^^^^^
File "D:\Users\liu3856\AppData\Local\Programs\Python\Python311\Lib\site-packages\meshio\_mesh.py", line 99, in __init__
self.dim = topological_dimension[cell_type]
~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^
KeyError: 'wedge15'
Because the geometry is complex, it’s hard to generate a high quality mesh without wedge elements. Is there an easy way to fix this?
I added "wedge15": 3, to topological_dimension defined in meshio\_mesh.py which solves the problem.
Have you resolved this issue? Your file works fine on my machine. This error probably means that your inputs to the glb file is wrong somewhere.
The problem with glb has been fixed. It turned out the glb file generated by the plug-in is incorrect.
@su.tian.22 @Wenbin
I am kind of baffled by swiftcomp complaining about distorted elements, because
The question is why does swiftcomp still complain about distorted element? Is there any workaround?
The error info is shown below.
command: swiftcomp wing3dSG_adjusted.sc 1D H
SwiftComp begins at 174437.937
Inputs echoed in file wing3dSG_adjusted.sc.ech!
Constitutive modeling for a 1D (beam) model!
Homogenization will be carried out!
You are running SwiftComp with full integration!
Finished reading/processing model file!
Effective properties can be found in file wing3dSG_adjusted.sc.k!
Finished homogenization!
SwiftComp ends at 174515.603
SwiftComp finished successfully!
command: swiftcomp wing3dSG_adjusted.sc 1D L
SwiftComp begins at 174547.983
Inputs echoed in file wing3dSG_adjusted.sc.ech!
Constitutive modeling for a 1D (beam) model!
Dehomogenization will be carried out!
You are running SwiftComp with full integration!
Finished reading/processing model file!
Local fields can be found in file wing3dSG_adjusted.sc.u and wing3dSG_adjusted.sc.sg and wing3dSG_adjusted.sc.sn!
Local fields in material coordinates can be found in wing3dSG_adjusted.sc.snm and wing3dSG_adjusted.sc.sgm!
determinant of Jacobian matrix less than 0 for element 501. The first several nodes of distorted element are: 18871 0.0000000000000000 4.1785046499999999E-002 -8.7108490999999993E-003 91588 0.0000000000000000 4.1499
It is indeed strange. You can send me your input file (sc and glb file) for me to debug.
@Wenbin
The file that I was using (wing3dSG_adjusted.sc) has very fine mesh, so I uploaded the one with coarser mesh.
You can download the sc file from here wing3dSG_archive.sc
do you know have another file for dehomogenization?
For dehomogenization, the results for the macroscopic beam is recorded in this file wing3dSG_archive.sc.glb
For testing, I set all strains to zero.
I can download the first file, but not the second file (glb file)
That is strange. I can download my own file using the link. If that doesn’t work for you, you may create wing3dSG_archive.sc.glb and copy the content below to wing3dSG_archive.sc.glb.
0.000000E+00 0.000000E+00 0.000000E+00
1.000000E+00 0.000000E+00 0.000000E+00
0.000000E+00 1.000000E+00 0.000000E+00
0.000000E+00 0.000000E+00 1.000000E+00
1
0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00
which version you used? on windows server?
