[Baden]

Hello all.

I have defined a SCHEME variable using the following TUI command:

(rp-var-define 'interrupt/flag 0 'interger #f)

Initially, the variable "interrupt/flag" has a value of 0, but this value is changed to 1 via UDF based on a certain condition. I want the simulation to stop once the variable is changed to 1, so I implemented the following in Solve - Execute Command panels:



However, when the value of ""interrupt/flag" is changed to 1, the following text appears in the console but the simulation continues without stopping.



Does anyone have any idea why the simulation is not properly being interrupted? There is remarkably little documentation on the SCHEME language and even less on cx-interrupt.

[pakk]

I think you made a typo in your scheme command, it should be integer and not interger.

On the question you asked: I have no idea, but I am interested in this way of working, it looks useful if it works. Do you get the same behavior when you manually press control-C?
I see the command (cx-interrupt-client) also exists, maybe this could be what you need?

[Baden]

Originally Posted by pakk

I think you made a typo in your scheme command, it should be integer and not interger.

On the question you asked: I have no idea, but I am interested in this way of working, it looks useful if it works. Do you get the same behavior when you manually press control-C?
I see the command (cx-interrupt-client) also exists, maybe this could be what you need?

The typo was not present when in the SCHEME command I used, but thank you for pointing that out.

Pressing control-C results in the same problem: the simulation says "Interrupting" but does not stop. However, pressing control-C twice properly stops the simulation. I also tried the "cx-interrupt-client" command, but it appeared to have no effect (the "Interrupting" text did not appear in the command window).

[pakk]

If control-C twice works, did you try to put (cx-interrupt) twice?

(if (> (rpgetvar 'interrupt/flag) 0) (begin (cx-interrupt) (cx-interrupt)))

[Baden]

Originally Posted by pakk

If control-C twice works, did you try to put (cx-interrupt) twice?

(if (> (rpgetvar 'interrupt/flag) 0) (begin (cx-interrupt) (cx-interrupt)))

I tried both of the following neither worked.

(if (> (rpgetvar 'interrupt/flag) 0) (begin (cx-interrupt) (cx-interrupt)))

(if (> (rpgetvar 'interrupt/flag) 0) (begin (cx-interrupt) (cx-interrupt-client)))

Pressing control-C twice gives the following message which I was unable to replicate with the latter of the two codes posted above.

[KevinZ09]

I've got little to no experience using the SCHEME language, but to me it almost seems like you need to interrupt twice because the first time it interrupts the iteration loop within the current time step and the second time it interrupts the time step loop. So perhaps there are different commands for that.

Did you consult the following website to get more information:

http://www.scheme.com/tspl4/

[pakk]

Originally Posted by Baden

Pressing control-C twice gives the following message which I was unable to replicate with the latter of the two codes posted above.

It looks like it should be some combination of (cx-interrupt) and (cx-interrupt-client). I tried a little bit, and with (cx-interrupt) I get the same response, but with (cx-interrupt-client) I get "()" instead of "Interrupting client...". I tried to add parameters, as in (cx-interrupt-client 0), (cx-interrupt-client 'test), but the response was the same every time.

My conclusion: I don't know how to do this, and don't know how to find out.

[Baden]

Originally Posted by pakk

It looks like it should be some combination of (cx-interrupt) and (cx-interrupt-client). I tried a little bit, and with (cx-interrupt) I get the same response, but with (cx-interrupt-client) I get "()" instead of "Interrupting client...". I tried to add parameters, as in (cx-interrupt-client 0), (cx-interrupt-client 'test), but the response was the same every time.

My conclusion: I don't know how to do this, and don't know how to find out.

I have encountered the same issue. Unless anyone on the forums knows any better, I believe this is a dead end.

[pakk]

If you can go to Fluent support, it might not be a dead end.

[Baden]

Originally Posted by pakk

If you can go to Fluent support, it might not be a dead end.

Unfortunately, this avenue is not available to me as a student user.

[Siba11]

Originally Posted by Baden

I have encountered the same issue. Unless anyone on the forums knows any better, I believe this is a dead end.

Hi,
I wrote this command in the 'Execute Command' dialog box to stop a transient simulation. (I initially took the value of 'interrupt/flag' as 5).

(if(>(rpgetvar 'interrupt/flag) 0) (set! mstop? #t))

Apparently, it's working, and the solution stops as soon as the condition is violated. I found this on youtube. But I don't have any further information about this command.

Also, if possible, could you guide me on the UDF part. I'm encountering some problem with the DEFINE_ADJUST UDF I wrote.

[AlexanderZ]

I believe that instead of

rpgetvar

should be

%rpgetvar

[kele]

[QUOTE=Siba11;835714]Hi,
I wrote this command in the 'Execute Command' dialog box to stop a transient simulation. (I initially took the value of 'interrupt/flag' as 5).

Hey friend, have you solved this problem yet? Currently, I am experiencing this issue. I am looking for help to solve the problem, here is my code. Run the code but FLUENT does not stop running.

[CODE](rp-var-define 'interrupt/flag 0 'integer #f)
(define (interrupt)
(if (> (%rpgetvar 'interrupt/flag) 0)
(cx-interrupt)))