ok, as I promise to solve the periodic condition problem for one of my collegues, so i decide give it a try.
http://www.cfd-online.com/Forums/fluent/28770-periodic-boundary-condition-shadow-pairs.html
use TUI: mesh/modify-zones/make-periodic choose your periodic boundary IDs as the input. Everything should go well and complete cells match on both sides should be found.
2014年10月22日星期三
2014年10月19日星期日
difference between fourier transform and wavelets
Haiz, sometimes when all the hope fade, you have to look for something which can cheers you up.
anyway, you still have to live for quite a long time.
so i move out the first step for digital signal processing
http://math.stackexchange.com/questions/279980/difference-between-fourier-transform-and-wavelets
et us say we are looking at the signal of the light emitted from a traffic light. So for some time it will be red, and for some time it will be green (ignore the yellow for now). If we take the Fourier transform of the observed frequency, we can say that
At some time the traffic light shows red. (We know frequency to infinite precision, and that the red part of the signal is non-zero.)
At some time the traffic light shows green.
But a functioning traffic light would have either red or green shown at a time, and not both. And if the traffic light malfunctions and shows both lights at the same time, we would still see from the Fourier transform
At some time the traffic light shows red.
At some time the traffic light shows green.
But if we take the wavelet transform we can sacrifice frequency precision to gain temporal information. So with the wavelet transform done on the working traffic light we may see
At parameter w which corresponds roughly to t(w) being 1 o'clock sharp and k(w) corresponding to red, the wavelet transform is large and non-zero. This can be taken to mean that sometime around 1 o'clock sharp (could be exactly 1 o'clock, could be 1 minute past, could be 30 second before) the light showed a color that is more or less red (could be a little bit purple, or maybe a little bit amber).
At parameter w which corresponds roughly to t(w) being 1 o'clock sharp and k(w) corresponding to green, the wavelet transform is almost zero. This can be taken to mean that at all the times around 1 o'clock (say plus or minus 2 minutes) the traffic light does not show any hint of green.
At parameter w which corresponds roughly to t(w) being five minutes past 1 and k(w) corresponding to green, the wavelet transform is large and non-zero. This would indicate that around 1:05 (maybe 1:06, or 1:04) the light shined greenish (could have a tinge of teal or a bit of yellow in it).
This would tell us that not only can the traffic light show both red and green lights, that at least at around 1 o'clock the light is working properly and only showing one light.
anyway, you still have to live for quite a long time.
so i move out the first step for digital signal processing
http://math.stackexchange.com/questions/279980/difference-between-fourier-transform-and-wavelets
et us say we are looking at the signal of the light emitted from a traffic light. So for some time it will be red, and for some time it will be green (ignore the yellow for now). If we take the Fourier transform of the observed frequency, we can say that
At some time the traffic light shows red. (We know frequency to infinite precision, and that the red part of the signal is non-zero.)
At some time the traffic light shows green.
But a functioning traffic light would have either red or green shown at a time, and not both. And if the traffic light malfunctions and shows both lights at the same time, we would still see from the Fourier transform
At some time the traffic light shows red.
At some time the traffic light shows green.
But if we take the wavelet transform we can sacrifice frequency precision to gain temporal information. So with the wavelet transform done on the working traffic light we may see
At parameter w which corresponds roughly to t(w) being 1 o'clock sharp and k(w) corresponding to red, the wavelet transform is large and non-zero. This can be taken to mean that sometime around 1 o'clock sharp (could be exactly 1 o'clock, could be 1 minute past, could be 30 second before) the light showed a color that is more or less red (could be a little bit purple, or maybe a little bit amber).
At parameter w which corresponds roughly to t(w) being 1 o'clock sharp and k(w) corresponding to green, the wavelet transform is almost zero. This can be taken to mean that at all the times around 1 o'clock (say plus or minus 2 minutes) the traffic light does not show any hint of green.
At parameter w which corresponds roughly to t(w) being five minutes past 1 and k(w) corresponding to green, the wavelet transform is large and non-zero. This would indicate that around 1:05 (maybe 1:06, or 1:04) the light shined greenish (could have a tinge of teal or a bit of yellow in it).
This would tell us that not only can the traffic light show both red and green lights, that at least at around 1 o'clock the light is working properly and only showing one light.
2014年9月12日星期五
ansys fsi problem I
O.K .so recently stuck in mesh in ansys fluid structure interaction.the mesh in transient structure does not work well.
It looks like there is still a long way to go.
keep on pops up
error updating cell solution in the transient structural system.
i guess most probably will need some luck
This error mostly returned while you have intersecting bodies in your problem geometry. just one of those bodies should be meshed and the other ones should be used as "Body of influence" at least in one "Sizing" feather.
I hope this could solve your problem.
Good Luck
http://www.cfd-online.com/Forums/ansys-meshing/93314-problem-updating-mesh-workbench.html
another one
The target body that you want to scope to needs to be selected as patch conforming tetrahedron - if you don't do this it will not modify the meshing (To make target body patch conforming right click on mesh, select insert -> method -> select target body --> then select method tetrahedron)
http://www.cfd-online.com/Forums/ansys-meshing/96051-bodies-influence-settings-problem.html
It looks like there is still a long way to go.
keep on pops up
error updating cell solution in the transient structural system.
i guess most probably will need some luck
This error mostly returned while you have intersecting bodies in your problem geometry. just one of those bodies should be meshed and the other ones should be used as "Body of influence" at least in one "Sizing" feather.
I hope this could solve your problem.
Good Luck
http://www.cfd-online.com/Forums/ansys-meshing/93314-problem-updating-mesh-workbench.html
another one
The target body that you want to scope to needs to be selected as patch conforming tetrahedron - if you don't do this it will not modify the meshing (To make target body patch conforming right click on mesh, select insert -> method -> select target body --> then select method tetrahedron)
http://www.cfd-online.com/Forums/ansys-meshing/96051-bodies-influence-settings-problem.html
2014年9月4日星期四
put the bracket beside the variable.
ok, so try orcad parameter sweep,
keep on pop up error,
**** INCLUDING SCHEMATIC1.net ****
* source RESISTORS
R_RS N02282 VL 47k TC=0,0
V_V1 N02282 0 10V
R_R1 0 VL rvariable TC=0,0
-----------------------------$
ERROR(ORPSIM-16152): Invalid number
.PARAM rvariable=10k
**** RESUMING "global sweep.cir" ****
.END
at the end is because i did not put the bracket beside the rvariable which is supposed to be parameter.
hehe, so stupid...
keep on pop up error,
**** INCLUDING SCHEMATIC1.net ****
* source RESISTORS
R_RS N02282 VL 47k TC=0,0
V_V1 N02282 0 10V
R_R1 0 VL rvariable TC=0,0
-----------------------------$
ERROR(ORPSIM-16152): Invalid number
.PARAM rvariable=10k
**** RESUMING "global sweep.cir" ****
.END
at the end is because i did not put the bracket beside the rvariable which is supposed to be parameter.
hehe, so stupid...
2014年9月3日星期三
Part VIN has no 'STIMULUS' property
Ok. so today I run the PSpice, and face the problem
INFO(ORNET-1041): Writing PSpice Flat Netlist C:\Cadence\SPB_16.6\OpenAccess\resistors-PSpiceFiles\SCHEMATIC1\SCHEMATIC1.net
ERROR(ORNET-1110): Part VIN has no 'STIMULUS' property
constantly make the error, whether i change Vac, Vdc, but life is always like this, you never realize you make the mistake only after you make it.
Hehe. I have extra component in the bottom page, that's why i have that error.
once I remove the extra component of power source, the error disappear.
remember at the start, you create a project based on simple.obj.using the design template.at the corner you can see the following figure, remove it.
as it create extra power source, that's why your simulation is not running, once you remove, our circuit is completed and in a closed loop, so everything is working fine.
hope it helps.
INFO(ORNET-1041): Writing PSpice Flat Netlist C:\Cadence\SPB_16.6\OpenAccess\resistors-PSpiceFiles\SCHEMATIC1\SCHEMATIC1.net
ERROR(ORNET-1110): Part VIN has no 'STIMULUS' property
constantly make the error, whether i change Vac, Vdc, but life is always like this, you never realize you make the mistake only after you make it.
Hehe. I have extra component in the bottom page, that's why i have that error.
once I remove the extra component of power source, the error disappear.
remember at the start, you create a project based on simple.obj.using the design template.at the corner you can see the following figure, remove it.
as it create extra power source, that's why your simulation is not running, once you remove, our circuit is completed and in a closed loop, so everything is working fine.
hope it helps.
2014年8月19日星期二
how to transfer netlist from Orcad Capture to Allegro?
O.K. so today learn how to transfer netlist from cadence orcad to allegro 16.
again, the cute window system do the foolish style.
I successfully generate the netlist from cadence orcad capture, and it open the allegro 16.
However, i cannot find the component when i click placed manaually,
I panicked...haiz
then i look online and find the post about cadence, but now i cannot retrieve the link.
so if you face the same problem like me and it is in window 8, so you know what i know.
run the orcad capture with right click , select it run as administrator.
then rerun the create netlist, you should be able to see the list of the componet in the placement box, i guess it is the same for any orcad PCB editor.
so cute windows 8, what the hell everytime i have problem with my excellent design software, the first thing i will think about is right click and click run as administrator...
haiz.
wish all the designer work the best!!!
again, the cute window system do the foolish style.
I successfully generate the netlist from cadence orcad capture, and it open the allegro 16.
However, i cannot find the component when i click placed manaually,
I panicked...haiz
then i look online and find the post about cadence, but now i cannot retrieve the link.
so if you face the same problem like me and it is in window 8, so you know what i know.
run the orcad capture with right click , select it run as administrator.
then rerun the create netlist, you should be able to see the list of the componet in the placement box, i guess it is the same for any orcad PCB editor.
so cute windows 8, what the hell everytime i have problem with my excellent design software, the first thing i will think about is right click and click run as administrator...
haiz.
wish all the designer work the best!!!
2014年7月13日星期日
FLUENT received fatal signal (ACCESS_VIOLATION)
How do I resolve the following error: FLUENT received fatal signal (ACCESS_VIOLATION)?
as referred to http://www.eureka.im/89.html
This is the standard error caused by FLUENT trying to access data that has not been allocated.
There are several causes which we will discuss.
For example, in a UDF, you may probe the cell temperature using the macro C_T(c,t). However, if you have not turned the energy equation on, then there is NO temperature stored, and you will get an ACCESS_VIOLATION.
To check a Thread for whether a variable is stored on it, you can use the THREAD_STORAGE(t, SV_XXX) macro, where SV_XXX is the storage variable for the equation of interest. For the energy equation, you would use SV_T. This macro returns a pointer to the data. The value is NULL if the data is not available. See storage.h for a complete list of storage variables.
Another cause for the macro is that your case has a UDF hooked, but you do not have the UDF available. The solution is to make sure you have the UDF directory in the correct location relative to the case file.
from
http://www.cfd-online.com/Forums/fluent/106319-fluent-received-fatal-signal-access_violation.html
This is what I would do but there is many not be it.
Do General -> Check to see whether there is anything obvious you are missing. This will also do the mesh check.
Change the Compute from options in the Standard Initialization and it will give different Initial Values below. See whether there is any boundary condition which give strange values (e.g. very high velocities or temperature)
Go throught the boundary conditions and check they are fine. If you still cannot see it turn all the boundary condition to wall except one inlet and one outlet and do initialization. If successful change back other boundary conditions to fish the error out.
Good luck.
as referred to http://www.eureka.im/89.html
This is the standard error caused by FLUENT trying to access data that has not been allocated.
There are several causes which we will discuss.
For example, in a UDF, you may probe the cell temperature using the macro C_T(c,t). However, if you have not turned the energy equation on, then there is NO temperature stored, and you will get an ACCESS_VIOLATION.
To check a Thread for whether a variable is stored on it, you can use the THREAD_STORAGE(t, SV_XXX) macro, where SV_XXX is the storage variable for the equation of interest. For the energy equation, you would use SV_T. This macro returns a pointer to the data. The value is NULL if the data is not available. See storage.h for a complete list of storage variables.
Another cause for the macro is that your case has a UDF hooked, but you do not have the UDF available. The solution is to make sure you have the UDF directory in the correct location relative to the case file.
from
http://www.cfd-online.com/Forums/fluent/106319-fluent-received-fatal-signal-access_violation.html
This is what I would do but there is many not be it.
Do General -> Check to see whether there is anything obvious you are missing. This will also do the mesh check.
Change the Compute from options in the Standard Initialization and it will give different Initial Values below. See whether there is any boundary condition which give strange values (e.g. very high velocities or temperature)
Go throught the boundary conditions and check they are fine. If you still cannot see it turn all the boundary condition to wall except one inlet and one outlet and do initialization. If successful change back other boundary conditions to fish the error out.
Good luck.
订阅:
博文 (Atom)