Subroutine print in adams

Hello,

Is there a way to print the outputs of a subroutine (C++) via the adams/vew or adams/solver windows (something similar to debug/eprint for example)? This far, the only way I've found to get some feedback when debugging my subroutines is via printing in .txt files.

Thanks,

Josef

Parents

0 Martin Kieltsch over 2 years ago

Depending where you compile & run, a normal print statement will do the job.

This is the case for Linux and the output is being send to the calling shell.

You'll find an example here:

simcompanion.hexagon.com/.../in-a-c-version-of-a-dll-code-i-am-trying-to-store-some-packages-of-property-parameters-as-a-linked-list-using-the-struct-node-concept-however-i-only-see-iflag-value-either-3-or-0-when-i-print-it-is-there-any-reason-that-i-do-not-see-iflag-1

I usually combine that with redirecting the output to a file and then opening that file in an editor :

mdi -c acar ru-acar i xxx.acf e > debug_output.txt ; nedit debug_output.txt

(Main reason is that this is much faster than printing everything into the shell plus it's easier to scroll & search in a text editor)

The bad news: In Windoze this doesn't work and you'll need to write to an own file ot use the USRMES/ERRMES.

In my experience the latter ones are incredibly slow for a larger amount of outout than writing to a file.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Martin Kieltsch over 2 years ago

Depending where you compile & run, a normal print statement will do the job.

This is the case for Linux and the output is being send to the calling shell.

You'll find an example here:

simcompanion.hexagon.com/.../in-a-c-version-of-a-dll-code-i-am-trying-to-store-some-packages-of-property-parameters-as-a-linked-list-using-the-struct-node-concept-however-i-only-see-iflag-value-either-3-or-0-when-i-print-it-is-there-any-reason-that-i-do-not-see-iflag-1

I usually combine that with redirecting the output to a file and then opening that file in an editor :

mdi -c acar ru-acar i xxx.acf e > debug_output.txt ; nedit debug_output.txt

(Main reason is that this is much faster than printing everything into the shell plus it's easier to scroll & search in a text editor)

The bad news: In Windoze this doesn't work and you'll need to write to an own file ot use the USRMES/ERRMES.

In my experience the latter ones are incredibly slow for a larger amount of outout than writing to a file.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data