Frank van Gool
COMSOL Employee
Please login with a confirmed email address before reporting spam
Posted:
10 years ago
Apr 30, 2015, 4:02 a.m. EDT
Dear Yuankang,
As mentioned in the other thread on this subject:
www.comsol.nl/community/forums/general/thread/47735/
You need to make sure that the axis are in the same "order" because COMSOL maps the points to a grid.
You need to multiply your time column with 1e9, so that the values are in ns.
Best regards,
Frank
Dear Yuankang,
As mentioned in the other thread on this subject:
https://www.comsol.nl/community/forums/general/thread/47735/
You need to make sure that the axis are in the same "order" because COMSOL maps the points to a grid.
You need to multiply your time column with 1e9, so that the values are in ns.
Best regards,
Frank
Gunnar Andersson
COMSOL Employee
Please login with a confirmed email address before reporting spam
Posted:
10 years ago
Apr 30, 2015, 8:40 a.m. EDT
You need to make sure that the axis are in the same "order" because COMSOL maps the points to a grid.
This used to be true a couple of versions ago, but this requirement has been lifted - the data is scaled internally if necessary.
The most common reason for the error message is that the point set is singular. E.g., for a function of 3 arguments, the point set consists of points that all lie on a line or plane. Multiphysics' interpolation function code can't handle that.
[QUOTE]
You need to make sure that the axis are in the same "order" because COMSOL maps the points to a grid.
[/QUOTE]
This used to be true a couple of versions ago, but this requirement has been lifted - the data is scaled internally if necessary.
The most common reason for the error message is that the point set is singular. E.g., for a function of 3 arguments, the point set consists of points that all lie on a line or plane. Multiphysics' interpolation function code can't handle that.
Please login with a confirmed email address before reporting spam
Posted:
10 years ago
Apr 30, 2015, 10:53 a.m. EDT
Dear Gunnar,
I did see some thread explaining the singulartiy of the set can be a problem when importing the data.
But in my case, all the points don't lie on a plan (If you go down to my data set, you ll see my third argument change).
I did what Frank suggested: multiple the third argument by 1e9 to make sure all the arguments are in the same or at least similar order. It works. It seems COMSOL hasn't lifted this requirement yet :(
Now I will try to use this three-argment function to set time and space dependent boudanry conditions.
Thank you guys for your help!
YK
Dear Gunnar,
I did see some thread explaining the singulartiy of the set can be a problem when importing the data.
But in my case, all the points don't lie on a plan (If you go down to my data set, you ll see my third argument change).
I did what Frank suggested: multiple the third argument by 1e9 to make sure all the arguments are in the same or at least similar order. It works. It seems COMSOL hasn't lifted this requirement yet :(
Now I will try to use this three-argment function to set time and space dependent boudanry conditions.
Thank you guys for your help!
YK
Please login with a confirmed email address before reporting spam
Posted:
10 years ago
Apr 30, 2015, 4:36 p.m. EDT
It appears there's a hole in the data, near the point, at t = 1.2e-8
It appears there's a hole in the data, near the point, at t = 1.2e-8
Please login with a confirmed email address before reporting spam
Posted:
10 years ago
Apr 30, 2015, 4:44 p.m. EDT
Oh really?
However I imported the data successfully. I ll check that. :0
Oh really?
However I imported the data successfully. I ll check that. :0