Skip to main content

MAPDL Tips 2: Exporting solution results to CSV file 


 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
! Provided that nvars 1-8 are properly defined earlier in the input file using the esol or nsol command, the following will export the results to the CSV file


! EXPORT RESULTS TO FILE BLOCK
!Create a table to export first
*DIM, ExportedResults,TABLE, itnCount,7
!ExportedResults(0,1) = 1 !Zeroth row
VGET,ExportedResults(1,0),1
VGET,ExportedResults(1,1),2
VGET,ExportedResults(1,2),3
VGET,ExportedResults(1,3),4
VGET,ExportedResults(1,4),5
VGET,ExportedResults(1,5),6
VGET,ExportedResults(1,6),7
VGET,ExportedResults(1,7),8

/output, 'Results','csv','.'
*VWRITE,'TIME','TEMP','DX','DY','DZ','RES1', 'RES2', 'RES3'
%C, %C, %C, %C, %C, %C, %C, %C
*VWRITE,ExportedResults(1,0),ExportedResults(1,1),ExportedResults(1,2),ExportedResults(1,3),ExportedResults(1,4),ExportedResults(1,5),ExportedResults(1,6),ExportedResults(1,7) 
%G, %G, %G, %G, %G, %G, %G, %G
/OUTPUT, TERM
! END EXPORT BLOCK
Labels:

Comments

Post a Comment

Productive comments only!!

Popular posts from this blog

SAVE PARAMETERS IN APDL TO USE IN POST-SOLVE

Often times, you define some parameters/variables using command snippets in ANSYS Mechanical's geometry or boundary commands. Scenarios exists when you need to use these variables to evaluate results in the Results section of the Mechanical. Now, usually when you run the entire Mechanical at once, these parameters get evaluated by MAPDL. However, when the problem takes long time to solve, and you would like to make changes to command snippets in the results section only, it's inconvenient to solve the whole model again just to evaluate the new results. Usually, MAPDL handles this by just issuing POST-SOLVE commands only. But, now since the parameters we defined earlier are out of scope here, the results utilizing these parameters are not properly evaluated. The remedy is the following commands: Step 1 : At the end of the pre-processing command snippet, use the command PARSAV to store parameters to file: Step 2: Prior to using other commands in the Results section's command ...
Post a Comment
Read more

USERMAT Compilation Fix for ANSYS with Intel oneAPI

 Issue with USERMAT Intel updated the Intel Parallel Studio XE  2019 to Intel oneAPI. Academic community relying on the free compiler license from Intel stopped getting renewed and are forced to use the newer oneAPI package. As a result the Fortran compiler+link for ANSYS stopped working with the new oneAPI (Well, "technically" compiler works, but the connection between ANSYS and Intel Package got broken).     So,  the line#109 within ANSUSERSHARED.BAT should be modified for the existing ANSYS installation to work with the new Intel oneAPI upgrade. I am assuming you know about the ANSUSERSHARED.BAT (and where to find it) since you have been compiling USERMAT before this Intel's update. TESTED WORKING SETUP  This tweak is tested only for the following setup: - Previous installation of Intel Parallel Studio XE 2019 update 3 - Current installation of Intel oneAPI 2021.1 (BaseKit + HPCKit) - ANSYS 2020 R1 Thanks.
Post a Comment
Read more