CFD Online Discussion Forums

CFD Online Discussion Forums (http://www.cfd-online.com/Forums/)
-   CFX (http://www.cfd-online.com/Forums/cfx/)
-   -   Minimal transient result lokks like full in Post (http://www.cfd-online.com/Forums/cfx/21441-minimal-transient-result-lokks-like-full-post.html)

Korsh Mik July 14, 2005 04:17

Minimal transient result lokks like full in Post
 
Dear Sirs,

The problem arose in CFX POST (5.7.1) - the transient results waere set as minimal, but in POST they are showed as Full, so the error arise when trying to load the result.

Where this problem could arise from?

Thank you!

Rui July 14, 2005 07:20

Re: Minimal transient result lokks like full in Po
 
Hi,

I didn't understant very well what you meant.But in Post the only result files you can load are: *.res, *_full.bak and *_full.trn. To have access to a *.trn file (minimal transient result) you have to go to the Timestep Selector.

Regards,

Rui

test July 14, 2005 08:01

Re: Minimal transient result lokks like full in Po
 
Hi, You should first load the results file or some backup file and then you can load the trn files (minimal)

Regards, test

Korsh Mik July 14, 2005 10:44

Re: Minimal transient result lokks like full in Po
 
It looks like you don't understand me.

I DO load the last result (res file) and in time selector I see al the transient resilts (trn files), but all of the trn files have type "Full". But they are not Full, they are Minimal, so when I try to load such file (in time selector) I get the error. The question was - why POST thinks that TRN files are FULL, while they are Minimal?

Rui July 14, 2005 12:09

Re: Minimal transient result lokks like full in Po
 
Hi,

In the folder created by CFX (where those files are located), are the files names, for example, 10.trn, 20.trn, etc?If so, I have no idea why Post shows them as Full.

What is exactly the error message you get?

Korsh Mik July 14, 2005 13:10

Re: Minimal transient result lokks like full in Po
 
I've gave the exact error as it should be when trying to load information about the domain from the file where there are no such info (from the minimal transient file) ;-)

Korsh Mik July 14, 2005 13:16

Re: Minimal transient result lokks like full in Po
 
So, the question is - where does POST obtain info about type of the transient file and why it's wrong. Or, it could be possible SOLVER wrote the wrong information into the TRN files? I have 3 sets of transient files in the definition - 2 sets are minimal and 1 is FULL... At the moment I can't say the exact error message as I'm not at the uni

Pete July 15, 2005 03:17

Re: Minimal transient result lokks like full in Po
 
Why have to complicate things for yourself? Just 3 trn files.... Make them all full.... It should work properly then...

Korsh Mik July 15, 2005 03:23

Re: Minimal transient result lokks like full in Po
 
Nice advice but not smart, as too much hard space wasted for unwanted data in full files

Rui July 15, 2005 10:14

Re: Minimal transient result lokks like full in Po
 
Hi,

Could you post here the OUTPUT CONTROL part of the .CCL file?

fpe July 15, 2005 22:30

Re: Minimal transient result lokks like full in Po
 
Ok.. You said it, but something is missing in your explanation. If you have 3 definitions for transient files: 1 Full and 2 Minimal, a what times, or time interval are these files being written.

The CFX-Solver will not write a minimal transient file if a full transient file be written at the same time step. Is this your case, perhaps? CFX-Post figures the existence of previous files from the results file, or a full transient file.

Hope it helps...

The more information you post describing your problem early on, the less iterations it will take for people here to help you.. Kind of an initial guess.

Good luck..

Korsh Mik July 18, 2005 04:16

Re: Minimal transient result lokks like full in Po
 
OUTPUT CONTROL:

BACKUP RESULTS: Backup Results 2

File Compression Level = Default

Iteration Interval = 25

Option = Full

Output Boundary Flows = All

Output Equation Residuals = All

END

MONITOR OBJECTS:

Monitor Coefficient Loop Convergence = On

MONITOR BALANCES:

Option = Full

END

MONITOR FORCES:

Option = Full

END

MONITOR PARTICLES:

Option = Full

END

MONITOR POINT: Monitor Points and Expressions 1

Expression Value = PressDrop

Option = Expression

END

MONITOR RESIDUALS:

Option = Full

END

MONITOR TOTALS:

Option = Full

END

END

RESULTS:

File Compression Level = Default

Option = Full

Output Equation Residuals = All

END

TRANSIENT RESULTS: Transient Results 1

File Compression Level = Default

Option = Minimal

Output Variables List = Pressure,Red,Total Pressure,Velocity

Time List = 0.05 [s], 0.15 [s]

END

TRANSIENT RESULTS: Transient Results 2

File Compression Level = Default

Option = Minimal

Output Variables List = Pressure,Red,Total Pressure,Velocity

Time Interval = 0.1 [s]

END

TRANSIENT RESULTS: Transient Results 3

File Compression Level = Default

Option = Full

Output Equation Residuals = All

Time Interval = 2 [s]

END

END

Rui July 18, 2005 10:44

Re: Minimal transient result lokks like full in Po
 
Hi,

I think everything is correct in your CCL file. You should have Minimal *.trn files with an interval of 0.1s (and at 0.05s and 0.15s), and Full *_full.trn files with an interval of 2s.

If all the transient files in the folder created by CFX are *_full.trn, the error is caused by the Solver; if there are *.trn files the error is probably caused by Post. But this won't help you.

Do you have the CFX-5.7.1 Patch installed? Do you see this at the biginning of the .out file?: Installed patches:

* CFX-5.7.1 Service Pack 1 build 200501312320If you have the Patch installed, I'm sorry but I have no idea why CFX-Post isn't reading the transient files correctly.

Regards,

Rui

Korsh Mik July 19, 2005 02:35

Re: Minimal transient result lokks like full in Po
 
The same patch and build. The names of the files:

19.07.2005 10:33 <DIR> . 19.07.2005 10:33 <DIR> .. 19.07.2005 10:33 0 1.txt 12.07.2005 09:01 206091581 197_full.trn 12.07.2005 09:25 21258330 198.trn 12.07.2005 09:47 21264293 199.trn 12.07.2005 10:10 21260418 200.trn 12.07.2005 10:34 21264859 201.trn 12.07.2005 10:57 21216082 202.trn 12.07.2005 11:20 21226206 203.trn 12.07.2005 11:42 21229082 204.trn 12.07.2005 12:05 21230501 205.trn 12.07.2005 12:28 21266113 206.trn 12.07.2005 12:51 21288174 207.trn 12.07.2005 13:14 21293890 208.trn 12.07.2005 13:37 21300941 209.trn 12.07.2005 14:00 21308294 210.trn 12.07.2005 14:25 21316214 211.trn 12.07.2005 14:49 21334982 212.trn 12.07.2005 15:13 21339373 213.trn 12.07.2005 15:38 21342363 214.trn 12.07.2005 16:02 21339282 215.trn 12.07.2005 16:26 21335497 216.trn 12.07.2005 16:51 21337310 217.trn 12.07.2005 17:15 21325325 218.trn 13.07.2005 17:53 273774483 219_full.trn 12.07.2005 18:05 21308285 220.trn 12.07.2005 18:29 21305094 221.trn 12.07.2005 18:53 21309039 222.trn 12.07.2005 19:17 21316357 223.trn 12.07.2005 19:41 21320706 224.trn 12.07.2005 20:05 21322998 225.trn 12.07.2005 20:30 21329634 226.trn 12.07.2005 20:55 21333399 227.trn 12.07.2005 21:19 21330206 228.trn 12.07.2005 21:43 21347138 229.trn 12.07.2005 22:07 21344273 230.trn 12.07.2005 22:31 21345497 231.trn 12.07.2005 22:55 21336602 232.trn 12.07.2005 23:19 21328886 233.trn 12.07.2005 23:43 21320077 234.trn 13.07.2005 00:07 21320194 235.trn 13.07.2005 00:31 21324214 236.trn 13.07.2005 00:55 21322730 237.trn 13.07.2005 01:19 21314154 238.trn 13.07.2005 17:53 273655226 239_full.trn 13.07.2005 02:09 21296237 240.trn 13.07.2005 02:33 21281438 241.trn 13.07.2005 02:57 21275178 242.trn 13.07.2005 03:21 21275510 243.trn 13.07.2005 03:45 21277208 244.trn 13.07.2005 04:09 21283174 245.trn 13.07.2005 04:33 21283453 246.trn 13.07.2005 04:57 21282014 247.trn 13.07.2005 05:21 21281221 248.trn 13.07.2005 05:45 21280810 249.trn 13.07.2005 06:09 21280285 250.trn 13.07.2005 06:35 21280533 251.trn 13.07.2005 06:59 21280794 252.trn 13.07.2005 07:23 21279630 253.trn 13.07.2005 07:47 21276718 254.trn 13.07.2005 08:11 21274146 255.trn 13.07.2005 08:35 21270918 256.trn 13.07.2005 08:59 21267405 257.trn 13.07.2005 09:23 21263526 258.trn 13.07.2005 17:53 273526050 259_full.trn 13.07.2005 10:12 21259090 260.trn 13.07.2005 10:36 21260298 261.trn 13.07.2005 11:00 21260237 262.trn 13.07.2005 11:24 21259645 263.trn 13.07.2005 11:48 21258822 264.trn 13.07.2005 12:12 21257050 265.trn 13.07.2005 12:36 21255782 266.trn 13.07.2005 13:00 21255321 267.trn 13.07.2005 13:24 21253358 268.trn 13.07.2005 13:48 21253089 269.trn 13.07.2005 14:13 21250029 270.trn 13.07.2005 14:37 21248378 271.trn 13.07.2005 15:01 21246193 272.trn 13.07.2005 15:25 21243926 273.trn 13.07.2005 15:50 21241026 274.trn 13.07.2005 17:53 21345008 275.trn 13.07.2005 17:53 273484692 275_full.bak 13.07.2005 16:39 21235786 276.trn 13.07.2005 17:03 21232533 277.trn 13.07.2005 17:28 21230299 278.trn

84 File(s) 2960925112 bytes

2 Dir(s) 1381548032 bytes free

Korsh Mik July 19, 2005 02:45

I've solved the problem by myself
 
I've just copied the results into another directory and after that it's all ok.

So the bug is inside POST, may be POST doesn't like long directory names.

Regards, Korshm


All times are GMT -4. The time now is 18:40.