[crevoise]

Hello all,

My concern is about how CCM could notify me that it reaches convergence of a time-step, and then start a new one.
It is possible to setup some auto-file, which export every time step some data. So I guess internally, CCM has some flag to notice it that the time step (let say the first) is over.

In StarCD, I had access to a flag 'LEVEL', corresponding to the export of the postdat file at every time step. Is there similar things for CCM?

Thanks for any hint

[rwryne]

You can have either tables (Tools->Tables) or Scenes "update" every timestep, writing out their data (for tables) or images (for scenes)

There is an update node to control this, change it from iteration based to time step based.

[crevoise]

Hello Rwyne

Thank you for your reply.
I forgot to noticed it in my first post so here are some more info about my concern.

I am currently trying to couple CCM with my own external code. In order to perform calculation on my code, I need the data from CCM on the last iteration of every time step.
I am accessing the data via User Function and give back for example source term.

So in that case, the solution you are proposing is not really suitable, unfortunately.
Do you have in mind any other tip?

Thank you in advance

/crevoise

[rwryne]

Originally Posted by crevoise

Hello Rwyne

Thank you for your reply.
I forgot to noticed it in my first post so here are some more info about my concern.

I am currently trying to couple CCM with my own external code. In order to perform calculation on my code, I need the data from CCM on the last iteration of every time step.
I am accessing the data via User Function and give back for example source term.

So in that case, the solution you are proposing is not really suitable, unfortunately.
Do you have in mind any other tip?

Thank you in advance

/crevoise

Then the table is what you want....specifically an XYZ internal table

You can tell it exactly what variables you want outputted, over which regions. It will then write out the data you want at the end of each timestep (if you set that up via the Update node). Then have your code check for the updated information. Make sure to check the "auto extract" button in addition to the "save to file" button

This could also be accomplished by writing a Java script to control STAR-CCM+s running more tightly... as in, tell it to run another timestep, output your data to text tile, and continue. Seems the table approach would be easier.