Menu

Discussion Forum

New Discussion
Filter

Note: This discussion is about an older version of the COMSOL Multiphysics® software. The information provided may be out of date.

Discussion Closed This discussion was created more than 6 months ago and has been closed. To start a new discussion with a link back to this one, click here.

Derived values in different tables instead of in 1 table

Posted May 17, 2013, 4:15 a.m. EDT Results & Visualization Version 4.3b, Version 4.4 4 Replies

Hans Parmentier
Send Private Message Flag post as spam

Please login with a confirmed email address before reporting spam

Sometimes the derived values are comming in 1 table when doing the clear and evaluate all.
But sometimes all the different values are comming in different tables which is not usefull to work with (copy paste becomes more difficult).
It appeared when adding calculated values after the probe values.

Somebody knows how this is triggered?

Hans
4 Replies Last Post Jun 27, 2014, 3:32 a.m. EDT
COMSOL Moderator

Hello Hans Parmentier

Your Discussion has gone 30 days without a reply. If you still need help with COMSOL and have an on-subscription license, please visit our Support Center for help.

If you do not hold an on-subscription license, you may find an answer in another Discussion or in the Knowledge Base.

Christian Walter
Send Private Message Flag post as spam

Please login with a confirmed email address before reporting spam

Posted: 1 decade ago Aug 19, 2013, 10:06 a.m. EDT
same problem here.

I want all the derived values to appear in one table. Sometimes this happens automatically, sometimes not.

Is there any solution to that problem? Because I couldn´t find any option where I can specify the table in which the derived values shall appear...
same problem here. I want all the derived values to appear in one table. Sometimes this happens automatically, sometimes not. Is there any solution to that problem? Because I couldn´t find any option where I can specify the table in which the derived values shall appear...
Fabio Greco
Send Private Message Flag post as spam

Please login with a confirmed email address before reporting spam

Posted: 1 decade ago Aug 19, 2013, 11:17 a.m. EDT
Hi Hans,

for the derived values that you use (Point or Global evaluation), on the button with the orange symbol of equal = (Evaluate button) there is the list of tables. Therefore, you can choose to store your values in a defined table or in a new table

Hope this helps
Regards
Hi Hans, for the derived values that you use (Point or Global evaluation), on the button with the orange symbol of equal = (Evaluate button) there is the list of tables. Therefore, you can choose to store your values in a defined table or in a new table Hope this helps Regards
Christian Walter
Send Private Message Flag post as spam

Please login with a confirmed email address before reporting spam

Posted: 1 decade ago Aug 20, 2013, 6:56 a.m. EDT
Thank you. That is exactly the option I was looking for!
Thank you. That is exactly the option I was looking for!
Steven Penn
Send Private Message Flag post as spam

Please login with a confirmed email address before reporting spam

Posted: 1 decade ago Jun 27, 2014, 3:32 a.m. EDT
While this proposed solution will work, it means that in order to combine all, or selected, derived values into a single table the program must recalculate the values, which is a waste of time for what should be a simple copy/paste operation.

Burying the table assignment in the evaluate menu obscures this option and unnecessarily links it to the evaluation. Instead there should a clear option in the derived value UI to indicate on which table a given value will be placed, and a correlated option in the table UI to define which values appear on a given table. If the values have already been calculated, then a change of these options should trigger a move or copy of the values to the new table. Then the table reconfiguration is clear and fast.
While this proposed solution will work, it means that in order to combine all, or selected, derived values into a single table the program must recalculate the values, which is a waste of time for what should be a simple copy/paste operation. Burying the table assignment in the evaluate menu obscures this option and unnecessarily links it to the evaluation. Instead there should a clear option in the derived value UI to indicate on which table a given value will be placed, and a correlated option in the table UI to define which values appear on a given table. If the values have already been calculated, then a change of these options should trigger a move or copy of the values to the new table. Then the table reconfiguration is clear and fast.

Note that while COMSOL employees may participate in the discussion forum, COMSOL® software users who are on-subscription should submit their questions via the Support Center for a more comprehensive response from the Technical Support team.

Suggested Content