[AlexanderZ]

Please, help me, if you can.

Problem description:
For User_Defined model in Fluent the GUI was developed using scheme language.
One of the feature of model is it's capability to stop simulation when the stop_criteria is met.
To make this, one approach was applied:
Start loop -> Make only one timestep iteration, than check stop_criteria in UDF. If stop_criteria is False, than repeat timestep iteration. If stop_criteria is True -> exit loop/stop simulation.
This approach works well, however, there is a great disadvantage.
Once the number of maximum repeats in loop is set and simulation starts, it is impossible to stop simulation at any moment.
Instead, we have to wait until stop_criteria is True or max repeat number.
GUI is not active when scheme script is working.

It is a big problem, if the wrong result is observed from the very beginning. For example: we want to simulate process 100 sec long, put 100 repeat numbers in loop of 1 sec time step -> total 100*1sec = 100 sec.
We may observe wrong result from 5sec, but can't stop simulation.

Question:

1. How can I modefy code to make it possible to stop solution any moment?
2. Are there other approaches to stop simulation when to stop_criteria is been met

Code example:

(define (my-iter max-iter)
    (do ((i 1 (+ i 1)) )
     ((or (> i max-iter)(%rpgetvar 'stop_criteria?)))          ; Get stop_criteria value from UDF part
     (rpsetvar 'physical-time-step (%rpgetvar 'model_time_step_size))   ; Set timestep size for new time iteration 
     (ti-menu-load-string (format #f "solve d-t-i 1 ~a" (%rpgetvar 'model_iteration_count))) ; Set number of internal iteratons for new time iteration
     (newline)
    )
   )

[AlexanderZ]

If anyone has the idea, how to solve this problem, please share.

I appreciate any help. Thanks in advance!

[AlexanderZ]

If anyone has the idea, how to solve this problem, please share.

I appreciate any help. Thanks in advance!

[KaLium]

does ctrl + C work?

[AlexanderZ]

Originally Posted by KaLium

does ctrl + C work?

Thank you for response! I really appreciate! However:

ctrl+C or ctrl+c double times is not the solution.
As i tried to describe, it is not ONLY ONE transient simulation,
but it is a LOOP of transient simulations.

Even if ctrl+C will stop one of them, the next one will start.

My scripts works this way -> example:

If I want to simulate 10 sec, I run a loop of 10 transient simulations 1 sec long
10times * 1sec = 10sec simulation.

The other problem, once script is running -> Fluent GUI becomes inactive

[AlexanderZ]

If anyone has the idea, how to solve this problem, please share.

I appreciate any help. Thanks in advance!

[ZAB]

A simple solution is to check for a specific file in your directory. if you can't find that file, set the 'stop_critera to true and jump out of loop

(if (file-exists? "someFile.txt") (display 'continue) (rpsetvar 'stop_criteria? #t))

all you have to do is delete that file, the above command will return false when it can't find or can't open the file, this way you can stop by deleting the file in folder.

you can put it here

(define (my-iter max-iter)
    (do ((i 1 (+ i 1)) )
     ((or (> i max-iter)(%rpgetvar 'stop_criteria?)))          ; Get stop_criteria value from UDF part
     (rpsetvar 'physical-time-step (%rpgetvar 'model_time_step_size))   ; Set timestep size for new time iteration 
     (ti-menu-load-string (format #f "solve d-t-i 1 ~a" (%rpgetvar 'model_iteration_count))) ; Set number of internal iteratons for new time iteration
     (newline)
     (if (file-exists? "someFile.txt") (display 'continue) (rpsetvar 'stop_criteria? #t))
    )
   )

[AlexanderZ]

To ZAB

Thank you for sharing! You approach should work for my case.

This is effective solution, however, a tricky one.
I wonder, do you know the way, how to stop scheme if it is already started?
For example, we can stop fluent using Ctrl+C, but for scheme it doesn't work.

Best regards,
Zorin Alexander

[ZAB]

I wonder, do you know the way, how to stop scheme if it is already started?

No, In my Understanding, Fluent Engine is running the scheme in Background. so probably only way to stop it properly would be by code itself.