posted by Ignacio Rocca at Feb 8, 2010 8:01 PM
Quote
Abul, thanks for your answers, it was very usefull, thanks for the recomendation of 5 orders of magnitude but I donīt find the paper, can you write the name for search it on internet!
best regards
Ignacio
posted by abul anuar at Feb 4, 2010 11:38 AM
Quote
i'm not sure whether you could have something like that.try putting some volume on the surface (try extruding the surface), and then reduce the volume 1 magnitude at a time.abul
posted by abul anuar at Feb 4, 2010 11:21 AM
Quote
Hi Nacho,i went through the paper again and its not 6 but 5. In the paper it states " The accuracy of the mesh generator GMSH currently limits the ratio between the simulation box size and the smallest cell size to of approximately 10^5". So if your computational box is 1 meter x 1 meter x 1 meter, the minimum cell size would be 10 microns (something like that). You do this by defining the resolution on the point you used to create the object (surface i guess). So, in you geo file the point will be like "Point(x) = {0,0,0,0.00001}, the fourth element represent the resolution of the points.I'll look at your geo if i had the time. most probably is the geometry error which leads to meshing error (although it is not really an error).abul
posted by Ignacio Rocca at Feb 3, 2010 3:29 PM
Quote
Thanks abul but I donīt understand very well what mean 6 orders of magnitude, in what paper appear it? Please, can you explain it in an example? For ohter hand, I did one CAD of my plane and this error appear on Jython Log
- Exception in thread Thread-2:
- Traceback (most recent call last):
- File "C:SpisSPIS_4_0_00_WindowsThirdPartJythonjython2.2Libthreading.py", line 414, in _Thread__bootstrap
- self.run()
- File "C:SpisSPIS_4_0_00_WindowsSpisUIBinTasksTaskJyTop.py", line 168, in run
- sharedSolver! 'SpisNumCaller' !.BuildSim(sharedData! 'AllMeshField' !, sharedData! 'AllDataField' !)
- File "C:SpisSPIS_4_0_00_WindowsSpisUIBinSpisNumCaller.py", line 183, in BuildSim
- sharedSolver! 'jytop' !.BuildSim(AllMeshField, AllDataField)
- File "C:SpisSPIS_4_0_00_WindowsSpisUIBinJyTop4.py", line 377, in BuildSim
- self.simu = NumTopFromUI(self.volMesh,
- java.lang.ArrayIndexOutOfBoundsException: java.lang.ArrayIndexOutOfBoundsException: 0
posted by Ignacio Rocca at Feb 3, 2010 3:28 PM
Quote
Thanks abul but I donīt understand very well what mean 6 orders of magnitude, in what paper appear it? Please, can you explain it in an example? For ohter hand, I did one CAD of my plane and this error appear on Jython Log*Exception in thread Thread-2:
*Traceback (most recent call last):
- File "C:SpisSPIS_4_0_00_WindowsThirdPartJythonjython2.2Libthreading.py", line 414, in _Thread__bootstrap
- self.run()
- File "C:SpisSPIS_4_0_00_WindowsSpisUIBinTasksTaskJyTop.py", line 168, in run
- sharedSolver! 'SpisNumCaller' !.BuildSim(sharedData! 'AllMeshField' !, sharedData! 'AllDataField' !)
- File "C:SpisSPIS_4_0_00_WindowsSpisUIBinSpisNumCaller.py", line 183, in BuildSim
- sharedSolver! 'jytop' !.BuildSim(AllMeshField, AllDataField)
- File "C:SpisSPIS_4_0_00_WindowsSpisUIBinJyTop4.py", line 377, in BuildSim
- self.simu = NumTopFromUI(self.volMesh,
posted by abul anuar at Feb 1, 2010 9:36 PM
Quote
Hi Nacho,If i'm not mistaken, the dimension between the largest and the smallest can be up to 6 orders of magnitude (you can check that in the paper in IEEE). All you need to do is to define high resolution on the point leading to the construction of the plane (the 4 points you need to create the plane). In your case, if the plane size not exceeding the 6 orders of magnitude rule, your meshing should be ok, else you'll be in big trouble. That's what i understand, forgive me if i'm wrong. abul
posted by Ignacio Rocca at Feb 1, 2010 2:43 PM
Quote
Hi all, I need to know if I can simulate two planes separated 50 um? If is it posible what kind of mesh I need to define? Thanks
Ignacio