[FluentStarter]

Hey guys,

i'm running simulations on a grid and for that I need a bash-script. But unfortunatelly i'm encountering some problems while searching for information how to write this scripts.

For example. Up to now I use the following script to run the simulation. But the simulation doesn't stop when it reaches the maximum step quantity specified in my sim.-file. Which line do i have to add for this?



package macro;

import java.util.*;

import star.common.*;

public class macrotest extends StarMacro {

public void execute() {
execute0();
}

private void execute0() {

Simulation simulation_0 =
getActiveSimulation();

ResidualPlot residualPlot_0 =
((ResidualPlot) simulation_0.getPlotManager().getPlot("Residuals") );

residualPlot_0.open();

simulation_0.getSimulationIterator().run();


}
}

[me3840]

This should stop with the stopping criterion if they are enabled, check that is the case. There's no need to open the residual plot in batch, you can take those lines out.

Also this is not a Bash script, this is Java.

[underrelaxed]

Originally Posted by FluentStarter

Hey guys,

i'm running simulations on a grid and for that I need a bash-script. But unfortunatelly i'm encountering some problems while searching for information how to write this scripts.

For example. Up to now I use the following script to run the simulation. But the simulation doesn't stop when it reaches the maximum step quantity specified in my sim.-file. Which line do i have to add for this?



package macro;

import java.util.*;

import star.common.*;

public class macrotest extends StarMacro {

public void execute() {
execute0();
}

private void execute0() {

Simulation simulation_0 =
getActiveSimulation();

ResidualPlot residualPlot_0 =
((ResidualPlot) simulation_0.getPlotManager().getPlot("Residuals") );

residualPlot_0.open();

simulation_0.getSimulationIterator().run();


}
}

If this is all the functionality you need in your macro, I would suggest a different approach using the standard Star-CCM+ commands one might use to submit via command line. This commands would be:

<INSTALL_PATH>/star/bin/starccm+ -np <# of cores> -batch <simulation filename> -licpath <port@licenseserver name>

Depending on your simulation needs and the configuration of your grid, use starccm+ -help to review additional options. I suspect you are using a job scheduler, so pay extra attention to the -batchsystem option. The above basic command typically is the last line of the script.

You indirectly stated that your shell is bash, but directly that you need a script in bash. #!/bin/bash will be the first line of the script. Make friends with your system administrator(s), as they should be able to help you build the guts of the script based on the details of the grid configuration.

Hope that helps and I didn't confuse you too much!

[me3840]

Originally Posted by underrelaxed

<INSTALL_PATH>/star/bin/starccm+ -np <# of cores> -batch <simulation filename> -licpath <port@licenseserver name>

This should be:
<INSTALL_PATH>/star/bin/starccm+ -np <# of cores> -batch <java script or command> -licpath <port@licenseserver name> <simulation filename>

The -batch command takes an argument of a macro or one of the 'simple' commands like run or mesh. The sim filename is an argument to the starccm+ binary.

[underrelaxed]

Both commands will work, but me3840 comments are more complete.

I should have been more clear. The macro shared originally only solves the model, and the suggestion is to omit the macro. -batch without any macro or smart arguments (like mesh or run) defaults to run.

[monkeymax]

Both commands will work, but best practice (based on ~8 years of using STAR-CCM+) is that you should have the sim file as your last argument and any macro filename immediately preceeding that.
It matters less now than it used to (i.e. STAR-CCM+ cares a lot less these days about the order of the arguments) but is still good to apply this principle.

[FluentStarter]

Thanks guys!