Turn off printing results on cmd screen

Provide easy-to-use, extensible software for modeling, simulating, controlling, and analyzing the neuromusculoskeletal system.
POST REPLY
User avatar
Sina Porsa
Posts: 99
Joined: Thu Feb 03, 2011 7:21 pm

Turn off printing results on cmd screen

Post by Sina Porsa » Tue Apr 12, 2011 12:01 am

Hi all,
I am using the "forward dynamic" tool to solve a "dynamic optimization" problem using MATLAB optimization toolbox.
As it's a dynamic optimization, it has lots of forward integrations and for each of them, the forward dynamic tool prints lots of data on cmd screen (An example of the printed data is provided at the end of this message.)
I am pretty sure that if I could turn this feature off, I would save time.
I tried " forward -S setup.xml > null" but it did not helped. Because it writes the same data in a file which is time consuming as well.
Is there any way so that I can turn this printing feature off?

Attachment (example of the data printed on cmd screen):
-------------------------------------------------------
This program includes software developed by the
Apache Software Foundation (http://www.apache.org/).
-------------------------------------------------------

Constructing tool from setup file MATLAB-FD-Setup.xml.

AbstractTool Result loading model 'c:\Sina\uni\Arm26DynamicOpt\2p2\Arm2DOF6Muscle.osim'
Updating Model file to latest format...
Loaded model Arm2DOF6Muscle from file c:\Sina\uni\Arm26DynamicOpt\2p2\Arm2DOF6Muscle.osim
-----------------------------------------------------------------------
Loaded library
-----------------------------------------------------------------------
-----------------------------------------------------------------------

Running tool Result.
No external loads will be applied (external loads file not specified).

Loading states from file c:\Sina\uni\Arm26DynamicOpt\2p2\arm2DOF6Muscle_InitialStates.sto.
Storage: file=c:\Sina\uni\Arm26DynamicOpt\2p2\arm2DOF6Muscle_InitialStates.sto (nr=1 nc=19)
Number of columns does not match in formStateStorage. Found 18 Expected 16.
Found 1 state vectors with time stamps ranging
from 0 to 0.
MODEL: Arm2DOF6Muscle

ANALYSES (0)

BODIES (3)
body[0] = ground (mass: 0) (inertia: 0 0 0 0 0 0 0 0 0)
body[1] = r_humerus (mass: 1.86457) (inertia: 0.01481 0 0 0 0.004551 0 0 0 0.013193)
body[2] = r_ulna_radius_hand (mass: 1.53432) (inertia: 0.019281 0 0 0 0.001571 0 0 0 0.020062)

ACTUATORS (6)
actuator[0] = TRIlong
actuator[1] = TRIlat
actuator[2] = TRImed
actuator[3] = BIClong
actuator[4] = BICshort
actuator[5] = BRA
numStates = 16
numCoordinates = 2
numSpeeds = 2
numActuators = 6
numBodies = 3
numConstraints = 0

STATES (16)
y[0] = r_shoulder_elev
y[1] = r_elbow_flex
y[2] = r_shoulder_elev_u
y[3] = r_elbow_flex_u
y[4] = TRIlong.activation
y[5] = TRIlong.fiber_length
y[6] = TRIlat.activation
y[7] = TRIlat.fiber_length
y[8] = TRImed.activation
y[9] = TRImed.fiber_length
y[10] = BIClong.activation
y[11] = BIClong.fiber_length
y[12] = BICshort.activation
y[13] = BICshort.fiber_length
y[14] = BRA.activation
y[15] = BRA.fiber_length


Integrating from 0 to 1.5
Printing results of investigation Result to c:\Sina\uni\Arm26DynamicOpt\2p2\.
Forward simulation time = 688ms

User avatar
Ayman Habib
Posts: 2248
Joined: Fri Apr 01, 2005 12:24 pm

RE: Turn off printing results on cmd screen

Post by Ayman Habib » Wed Apr 13, 2011 10:17 am

Hi Sina,

The messages are written to stdout (in Programming terms), so if you can redirect that from within Matlab it should work, otherwise please file a feature request (from the application's Help->Request Features menu) and we'll try adding an option to work in quiet mode where info messages are not printed to stdout. Other than cluttering the screen, are there any more difficulties caused by these messages?

Best regards,
-Ayman

User avatar
Sina Porsa
Posts: 99
Joined: Thu Feb 03, 2011 7:21 pm

RE: Turn off printing results on cmd screen

Post by Sina Porsa » Wed Apr 13, 2011 4:59 pm

Hi Ayman
Unfortunately it seems that it is not possible to redirect it from matlab. I will send a feature request,
The problem is not clutter on the screen, but the time. For my specific forward dynamic problem, if I could turn off the screen display, I would save 20% of total time. For my final full scale runs which would take around 2 weeks, I will save 3 days for each run.

Regards,
Sina

POST REPLY