Please login with a confirmed email address before reporting spam
Posted:
10 years ago
22 mai 2015, 07:11 UTC−4
Probably your time stepping does not coincide with the stepwise function.
Lasse
Probably your time stepping does not coincide with the stepwise function.
Lasse
Please login with a confirmed email address before reporting spam
Posted:
10 years ago
22 mai 2015, 07:59 UTC−4
Probably your time stepping does not coincide with the stepwise function.
Lasse
Hi Lasse,
Thanks for you answer. But I still have a question. How to understand that the time not coincide with the stepwise function? Because at first period, the result at 0 to 0.125s is correctly 1, but after that, the result of function is always 0. I'm sure that the stepwise function is correct, because I have also seen the waveform, every second it has a high value.
[QUOTE]
Probably your time stepping does not coincide with the stepwise function.
Lasse
[/QUOTE]
Hi Lasse,
Thanks for you answer. But I still have a question. How to understand that the time not coincide with the stepwise function? Because at first period, the result at 0 to 0.125s is correctly 1, but after that, the result of function is always 0. I'm sure that the stepwise function is correct, because I have also seen the waveform, every second it has a high value.
Please login with a confirmed email address before reporting spam
Posted:
10 years ago
22 mai 2015, 08:03 UTC−4
I mean that when the solver takes time steps, it may jump over your pulse. I had this problem a few years ago, when I had a very short pulse every hour. I had to define solver time stepping explicitly so that the solver was able to "see" the pulses.
Lasse
I mean that when the solver takes time steps, it may jump over your pulse. I had this problem a few years ago, when I had a very short pulse every hour. I had to define solver time stepping explicitly so that the solver was able to "see" the pulses.
Lasse
Please login with a confirmed email address before reporting spam
Posted:
10 years ago
22 mai 2015, 08:07 UTC−4
I mean that when the solver takes time steps, it may jump over your pulse. I had this problem a few years ago, when I had a very short pulse every hour. I had to define solver time stepping explicitly so that the solver was able to "see" the pulses.
Lasse
Thanks Lasse. I have upload some pictures about the waveform, the temperature, temperature distribution at 0.1s, at 1.1s. So the problem is the temperature at 1.1s.
[QUOTE]
I mean that when the solver takes time steps, it may jump over your pulse. I had this problem a few years ago, when I had a very short pulse every hour. I had to define solver time stepping explicitly so that the solver was able to "see" the pulses.
Lasse
[/QUOTE]
Thanks Lasse. I have upload some pictures about the waveform, the temperature, temperature distribution at 0.1s, at 1.1s. So the problem is the temperature at 1.1s.
Please login with a confirmed email address before reporting spam
Posted:
10 years ago
22 mai 2015, 08:11 UTC−4
And I have defined the time step range(0,0,1,30). I think with the step of 0.1s it has enough time to see the impulse.
And I have defined the time step range(0,0,1,30). I think with the step of 0.1s it has enough time to see the impulse.
Please login with a confirmed email address before reporting spam
Posted:
10 years ago
22 mai 2015, 08:30 UTC−4
You have yellow color in the temperature definition. Check the units in the function definition: argument in seconds, function in K.
Your step is 0.1 s but the step 0.125 s. I wonder if that is enough. Have you tried "range(0,0.0625,30)?"
I do not remember any more how I did my model, it was Comsol version 3.5 and the year was 2009.
You have yellow color in the temperature definition. Check the units in the function definition: argument in seconds, function in K.
Your step is 0.1 s but the step 0.125 s. I wonder if that is enough. Have you tried "range(0,0.0625,30)?"
I do not remember any more how I did my model, it was Comsol version 3.5 and the year was 2009.
Please login with a confirmed email address before reporting spam
Posted:
10 years ago
22 mai 2015, 09:02 UTC−4
You have yellow color in the temperature definition. Check the units in the function definition: argument in seconds, function in K.
Your step is 0.1 s but the step 0.125 s. I wonder if that is enough. Have you tried "range(0,0.0625,30)?"
I do not remember any more how I did my model, it was Comsol version 3.5 and the year was 2009.
I have input the argument in seconds and function in K, and change the step rage(0,0.0625,30). But the definition of temperature is still in yellow and the results are nearly the same. there is no high temperature after 1sec.
[QUOTE]
You have yellow color in the temperature definition. Check the units in the function definition: argument in seconds, function in K.
Your step is 0.1 s but the step 0.125 s. I wonder if that is enough. Have you tried "range(0,0.0625,30)?"
I do not remember any more how I did my model, it was Comsol version 3.5 and the year was 2009.
[/QUOTE]
I have input the argument in seconds and function in K, and change the step rage(0,0.0625,30). But the definition of temperature is still in yellow and the results are nearly the same. there is no high temperature after 1sec.
Please login with a confirmed email address before reporting spam
Posted:
10 years ago
23 mai 2015, 06:38 UTC−4
Do you still have argument name x, as in your jpg-image?
Do you still have argument name x, as in your jpg-image?