[aerospain]

Hi all,

Another puzzling situation. Sometimes, reconstructPar works as expected, I ask for time 1000, for example, and I get the solution at 1000. But, some other times, this utility calculates the solutions at 990, like it is just doing now.

Any thoughts?

Thanks!

[wyldckat]

Hi aerospain,

I vaguely remember about a bug report, where it was described something like reconstructing "999.9999" should either be or not be the same as "1000"... maybe this is related to the same issue?

What was the exact command you used for the reconstruction?

Best regards,
Bruno

[aerospain]

Originally Posted by wyldckat

Hi aerospain,

I vaguely remember about a bug report, where it was described something like reconstructing "999.9999" should either be or not be the same as "1000"... maybe this is related to the same issue?

What was the exact command you used for the reconstruction?

Best regards,
Bruno

Hello again wyldckat,

The exact command I used was: reconstructPar -time 1000

I also tried a list of times comma-separated, but canceled operation when I saw 990 as the time being created.

Cheers!

[wyldckat]

Hi aerospain

Originally Posted by aerospain

I also tried a list of times comma-separated, but canceled operation when I saw 990 as the time being created.

Mmm... interesting... can you indicate the parameters used in "controlDict"? Mainly the ones related to time and writing the time folders?

Another thing is the files located at "processor*/1000/uniform/time". They should contain specific time information. Do they have anything out of the ordinary? Can you share one of these specific "uniform/time" files?

Best regards,
Bruno

[aerospain]

Hello wyldckat,

Are these the lines you were asking for?
/////////////////////////////////////
startFrom latestTime;
startTime 0;
stopAt endTime;
endTime 5000;
deltaT 1;
writeControl timeStep;
writeInterval 500;
purgeWrite 1;
/////////////////////////////////////

I think I've unravelled what has happened. I have told my solver to write every 500 iterations, but purgeWrite deletes what has been written at those steps every time a 500 iterations interval has gone by.

Now, why does "reconstructPar" give me results at 990 iterations??? BECAUSE, I have defined some functions inside "controlDict" to get forces, coefficients and probes every 10 iterations. But, I don't know if the information inside those folders is the same as the one we can get when written out results.

Regarding your petition for a "processor*/1000/uniform/time" I cannot send you anything because I have no "time" file or directory inside the "uniform" directory. What I do have is a fieldAveragingProperties file. But, the directory 1000 does not exist as explained above.

Therefore, wyldckat, thank you once again for your time, following your instructions I could see the elephant in front of me ;-)

cheers!