FAST.Farm

Dear Jiaping.Cui,

C_FLOAT is a named constant from the intrinsic ISO_C_BINDING module used for C interoperability within Fortran used to represent the kind of a single-precision floating point number. REAL() is an intrinsic function to convert a value to a real type.

paramTurbine in the super controller stores the turbine-dependent parameters (constants) of the super controller. In the super controller example, paramTurbine stores the frequency of a sinusoidal yaw rate in rad/s. For a 3-turbine wind farm (nTurbines = 3), the first turbine has a frequency of (3-1)*0.1 = 0.2 rad/s, the second turbine has a frequency of (3-2)*0.1 = 0.1 rad/s and the third turbine has a frequency of (3-3)*0.1 = 0 rad/s. from_SC in the super controller stores the turbine-dependent inputs to the individual turbine controllers from the super controller. In the super controller example, from_SC stores the demanded yaw rate in rad/s. The yaw demanded yaw rate is zero at time zero, but at other times, the amplitude is 0.05 rad/s (see line 168 in the sample sc_dll.f90). Please note that this is just a simple example to illustrate how to implement a super controller within FAST.Farm. The logic in this super controller example is very simple, but obviously, you can implement whatever logic you need.

Nothing recently, but the super controller available in FAST.Farm is documented here within the FAST.Farm User’s Guide and Theory Manual:
openfast.readthedocs.io/en/main … controller
openfast.readthedocs.io/en/main … eory-basis

Best regards,

1 Like

Dear Younes,

I debugged the issue you reported on Jul 06, 2021 and implemented a simple fix. Please find the details at the following pull request on the OpenFAST github site: github.com/OpenFAST/openfast/pull/839, which is currently undergoing review before being merged. Thanks for describing the problem and sharing your files. This made debugging much easier!

Best regards,

Dear Jason,

Thank you for the information, It makes me happy to know that I could help! I will download the last version of OpenFAST.

Thank you again and have a great day

Kindest regards

Dear Jason,

I would love to compute the power output of a wind farm of 5 wind turbines in FAST.Farm, in case of different wind directions, to see how much the wake effect impacts the wind farm power depending on the wind direction. The wind turbines are always yawed in the wind direction. Therefore, for each wind direction “WD”, I put “PropagationDir=-WD” in the InflowWind.dat Input file and “NacYaw=WD” for each wind turbine ElastoDyn.dat Input file.
For wind direction below 30 degrees (WD<30°), it works perfectly. But beyond this value, I get the following error:

************************************************************************************************** 
FAST.Farm 
 
Copyright (C) 2021 National Renewable Energy Laboratory 
Copyright (C) 2021 Envision Energy USA LTD 
 
This program is licensed under Apache License Version 2.0 and comes with ABSOLUTELY NO WARRANTY. 
See the "LICENSE" file distributed with this software for details. 
************************************************************************************************** 
 
FAST.Farm-Unversioned from c427ea2f4d069f9455680f5bb524449b70f051d5 
Compile Info: 
 - Compiler: Intel(R) Fortran Compiler 2021 
 - Architecture: 64 bit 
 - Precision: single 
 - OpenMP: No 
 - Date: Sep 30 2021 
 - Time: 09:19:24 
Execution Info: 
 - Date: 09/30/2021 
 - Time: 15:35:23+0200 
 
 Heading of the FAST.Farm input file: 
   Sample FAST.Farm input file 
Running AWAE. 
Running InflowWind. 
Running Super Controller. 
Running WakeDynamics. 
Running FASTWrapper (v1.00.00, 7-Feb-2017). 
Running OpenFAST. 
OpenFAST input file heading: 
    FAST Certification Test #26: NREL 5.0 MW Baseline Wind Turbine (Onshore) 
 
Running ElastoDyn. 
Nodal outputs section of ElastoDyn input file not found or improperly formatted. 
Running AeroDyn. 
AD15 Nodal Outputs: Nodal output section of AeroDyn input file not found or improperly formatted. 
Skipping nodal outputs. 
Running InflowWind. 
Running ServoDyn. 
Running ServoDyn Interface for Bladed Controllers (using Intel Visual Fortran for Windows, ). 
Using legacy Bladed DLL interface. 
Running OpenFAST. 
OpenFAST input file heading: 
    FAST Certification Test #26: NREL 5.0 MW Baseline Wind Turbine (Onshore) 
 
Running ElastoDyn. 
Nodal outputs section of ElastoDyn input file not found or improperly formatted. 
Running AeroDyn. 
AD15 Nodal Outputs: Nodal output section of AeroDyn input file not found or improperly formatted. 
Skipping nodal outputs. 
Running InflowWind. 
Running ServoDyn. 
Running ServoDyn Interface for Bladed Controllers (using Intel Visual Fortran for Windows, ). 
Using legacy Bladed DLL interface. 
Running OpenFAST. 
OpenFAST input file heading: 
    FAST Certification Test #26: NREL 5.0 MW Baseline Wind Turbine (Onshore) 
 
Running ElastoDyn. 
Nodal outputs section of ElastoDyn input file not found or improperly formatted. 
Running AeroDyn. 
AD15 Nodal Outputs: Nodal output section of AeroDyn input file not found or improperly formatted. 
Skipping nodal outputs. 
Running InflowWind. 
Running ServoDyn. 
Running ServoDyn Interface for Bladed Controllers (using Intel Visual Fortran for Windows, ). 
Using legacy Bladed DLL interface. 
Running OpenFAST. 
OpenFAST input file heading: 
    FAST Certification Test #26: NREL 5.0 MW Baseline Wind Turbine (Onshore) 
 
Running ElastoDyn. 
Nodal outputs section of ElastoDyn input file not found or improperly formatted. 
Running AeroDyn. 
AD15 Nodal Outputs: Nodal output section of AeroDyn input file not found or improperly formatted. 
Skipping nodal outputs. 
Running InflowWind. 
Running ServoDyn. 
Running ServoDyn Interface for Bladed Controllers (using Intel Visual Fortran for Windows, ). 
Using legacy Bladed DLL interface. 
Running OpenFAST. 
OpenFAST input file heading: 
    FAST Certification Test #26: NREL 5.0 MW Baseline Wind Turbine (Onshore) 
 
Running ElastoDyn. 
Nodal outputs section of ElastoDyn input file not found or improperly formatted. 
Running AeroDyn. 
AD15 Nodal Outputs: Nodal output section of AeroDyn input file not found or improperly formatted. 
Skipping nodal outputs. 
Running InflowWind. 
Running ServoDyn. 
Running ServoDyn Interface for Bladed Controllers (using Intel Visual Fortran for Windows, ). 
Using legacy Bladed DLL interface. 
 Time: 0 of 500 seconds. 
 
T1:FARM_InitialCO:FWrap_t0:FAST_Solution0:CalcOutputs_And_SolveForInputs:SolveOption2:SolveOption2 
c_Inp2AD_SrvD:InflowWind_CalcOutput:CalcOutput:IfW_4Dext_CalcOutput [position=(-37.812, -12.209, 
68.327) in wind-file coordinates]:Interp4D:Outside the grid bounds. 
SolveOption2:SrvD_CalcOutput:DLL_controller_call:Running with torque and pitch control of the 
NREL offshore 5MW baseline wind turbine from DISCON.dll as written by J. Jonkman of NREL/NWTC for 
use in the IEA Annex XXIII OC3 studies. 
T2:FARM_InitialCO:FWrap_t0:FAST_Solution0:CalcOutputs_And_SolveForInputs:SolveOption2:SolveOption2 
c_Inp2AD_SrvD:InflowWind_CalcOutput:CalcOutput:IfW_4Dext_CalcOutput [position=(-47.694, -14.079, 
62.514) in wind-file coordinates]:Interp4D:Outside the grid bounds. 
SolveOption2:SrvD_CalcOutput:DLL_controller_call:Running with torque and pitch control of the 
NREL offshore 5MW baseline wind turbine from DISCON.dll as written by J. Jonkman of NREL/NWTC for 
use in the IEA Annex XXIII OC3 studies. 
T3:FARM_InitialCO:FWrap_t0:FAST_So

a 
 
 Aborting FAST.Farm. 

Do you have an idea how to overcome the issue? I see that in the error message, it says “…Outside the grid bounds.”, but I don’t understand why since all the wind turbines are yawed within the wind direction, so it is similar to having the wind direction at 0° (X wise) and rotate the whole wind farm instead with WD.
What do you suggest me to do ?

Sorry for the inconvenience

Kindest regards

Younes

Dear Younes,

The FAST.Farm User’s Guide and Theory Manual recommends against setting PropogationDir different from zero when using Mod_AmbWind = 2 or 3 (InflowWind): openfast.readthedocs.io/en/main … nput-files. This setting is recommend so that the turbulence box used by InflowWind (e.g., from TurbSim) can be aligned with the FAST.Farm low- and high-resolution domains to avoid excess interpolation. As such, when using TurbSim to generate inflow, we find it easier to move the wind turbines within FAST.Farm than to change the wind direction.

If you are using uniform instead of turbulent wind, the nonzero setting of PropogationDir is less of a concern. Which type of inflow in InflowWind are you using?

Best regards,

1 Like

Dear Jason,

Thank you for the information and help! I am using steady wind (WindType = 1). I just realized that the wind turbine goes outside the high-resolution domain for those yaw angles, as you can see in the image below (left). So I adjusted everything (right figure) so that even for a yaw angle =90°, the wind turbine stays inside the high-resolution domain, and everything worked perfectly.

Thank you for the information about TurbSim, because I will use it for turbulence later. In this case, I will rotate the wind farm instead of changing the wind direction.

Kindest regards

Younes

Dear Jason,

Could you please guide me how to generate “SC_DLL.so” for Linux machine in Fast.Farm?

Best regards,
Hamid

Dear Jason,
I encounter the following problem when I try to run FAST.Farm with super controller, I wonder what go wrong?

[code]FAST.Farm

Copyright (C) 2021 National Renewable Energy Laboratory
Copyright (C) 2021 Envision Energy USA LTD

This program is licensed under Apache License Version 2.0 and comes with ABSOLUTELY NO WARRANTY.
See the “LICENSE” file distributed with this software for details.


FAST.Farm-Unversioned from ad768924600d2027fc6ae062de19ed668dbc1f57
Compile Info:

  • Compiler: Intel(R) Fortran Compiler 2021
  • Architecture: 64 bit
  • Precision: single
  • OpenMP: No
  • Date: May 07 2021
  • Time: 12:13:15
    Execution Info:
  • Date: 11/02/2021
  • Time: 15:49:07+0800

Heading of the FAST.Farm input file:
Sample FAST.Farm input file
Running AWAE.
Running InflowWind.
forrtl: severe (157): Program Exception - access violation
Image PC Routine Line Source[/code]
Best regards,
Liye

Dear Liye.Zhao,

This error message is not very descriptive. Can you clarify:

  • how you compiled FAST.Farm (from where did you obtain the source code, did you modify it in any way, and how did you compile)?
  • what FAST.Farm model you are running (from where did you obtain the input file(s) and what did you modify in them)?
  • which super controller are you using (from where did you obtain the source code, did you modify it in any way, and how did you compile)?

Best regards,

Dear Hamid,

Rafael Mudafort has now answered your Linux compiling related question on the issues page of the OpenFAST GitHub repository–see: github.com/OpenFAST/openfast/issues/909.

Best regards,

Dear Jason,
(1) I obtained FAST.Farm from github on May 7, 2021, I did not modify it anywhere, I compiled it in Visual stdio 2019.
(2) FAST.Farm input file is the old version, then I modified it according to the instruction manual in some parts, please see the attachments.
(3) I did not modify super controller source code, but I modifed DISCON in this part. Please see in attachments.

Your reply reminded me that I was worried about the version, so today I downloaded and compiled the new fast.farm_x64 from GitHub.And then I had this problem.

[code]FAST.Farm

Copyright (C) 2021 National Renewable Energy Laboratory
Copyright (C) 2021 Envision Energy USA LTD

This program is licensed under Apache License Version 2.0 and comes with ABSOLUTELY NO WARRANTY.
See the “LICENSE” file distributed with this software for details.


FAST.Farm-Unversioned from 7a59bec859b7111d009842789a369c65df357927
Compile Info:

  • Compiler: Intel(R) Fortran Compiler 2021
  • Architecture: 64 bit
  • Precision: single
  • OpenMP: No
  • Date: Oct 07 2021
  • Time: 20:45:35
    Execution Info:
  • Date: 11/03/2021
  • Time: 16:23:53+0800

Heading of the FAST.Farm input file:
Sample FAST.Farm input file
Running AWAE.
Running Super Controller.
Running WakeDynamics.
Running FASTWrapper (v1.00.00, 7-Feb-2017).
Running OpenFAST.
OpenFAST input file heading:
FAST Certification Test #18: NREL 5.0 MW Baseline Wind Turbine (Onshore)

Running ElastoDyn.
Nodal outputs section of ElastoDyn input file not found or improperly formatted.
Running AeroDyn.
AD15 Nodal Outputs: Nodal output section of AeroDyn input file not found or improperly formatted.
Skipping nodal outputs.
Running InflowWind.
Running ServoDyn.
Running ServoDyn Interface for Bladed Controllers (using Intel Visual Fortran for Windows, ).
Using legacy Bladed DLL interface.
Running OpenFAST.
OpenFAST input file heading:
FAST Certification Test #18: NREL 5.0 MW Baseline Wind Turbine (Onshore)

Running ElastoDyn.
Nodal outputs section of ElastoDyn input file not found or improperly formatted.
Running AeroDyn.
AD15 Nodal Outputs: Nodal output section of AeroDyn input file not found or improperly formatted.
Skipping nodal outputs.
Running InflowWind.
Running ServoDyn.
Running ServoDyn Interface for Bladed Controllers (using Intel Visual Fortran for Windows, ).
Using legacy Bladed DLL interface.
Running OpenFAST.
OpenFAST input file heading:
FAST Certification Test #18: NREL 5.0 MW Baseline Wind Turbine (Onshore)

Running ElastoDyn.
Nodal outputs section of ElastoDyn input file not found or improperly formatted.
Running AeroDyn.
AD15 Nodal Outputs: Nodal output section of AeroDyn input file not found or improperly formatted.
Skipping nodal outputs.
Running InflowWind.
Running ServoDyn.
Running ServoDyn Interface for Bladed Controllers (using Intel Visual Fortran for Windows, ).
Using legacy Bladed DLL interface.
PS E:\OpenFAST-5-7\Fast.Farm>
[/code]

Now I don’t know what to do. Besides, I downloaded and compiled the new discon.dll file today.

best regard,
Liye.

Dear Jason,
Due to network reasons, the FAST.Farm input file was not uploaded, so I show it here.

best regard,
Liye

Dear Liye.Zhao,

Does your DISCON controller at the turbine level have three super-controller arguments or only two? There should be three super-controller arguments to DISCON, including from_SCglob and from_SC as inputs and to_SC as an output. I don’t see that you have from_SCglob. A template of the source code at the turbine level (DISCON_SC.f90) is located in the reg_tests\r-test\glue-codes\fast-farm\5MW_Baseline\ServoData\DISCON directory of the OpenFAST/FAST.Farm repository. More information on the super controller is available in the online FAST.Farm documentation on readthedocs: openfast.readthedocs.io/en/main … controller.

Best regards,

Dear Jason,
Thank you very much for your patient answer!The DISCON file I used is the source file at the path you specified,And I added from_SCglob as input. When I run the FAST.Farm, I have this problem again. Could you please send me an example of fast. Farm successfully using super controller, so that I can compare with my own, I would be very grateful, so that I may find more problems that haven’t been found yet.Thanks very much!
Best regard,
Liye

[code]FAST.Farm

Copyright (C) 2021 National Renewable Energy Laboratory
Copyright (C) 2021 Envision Energy USA LTD

This program is licensed under Apache License Version 2.0 and comes with ABSOLUTELY NO WARRANTY.
See the “LICENSE” file distributed with this software for details.


FAST.Farm-Unversioned from 7a59bec859b7111d009842789a369c65df357927
Compile Info:

  • Compiler: Intel(R) Fortran Compiler 2021
  • Architecture: 64 bit
  • Precision: single
  • OpenMP: No
  • Date: Oct 07 2021
  • Time: 20:45:35
    Execution Info:
  • Date: 11/04/2021
  • Time: 09:57:10+0800

Heading of the FAST.Farm input file:
Sample FAST.Farm input file
Running AWAE.
Running Super Controller.
Running WakeDynamics.
Running FASTWrapper (v1.00.00, 7-Feb-2017).
Running OpenFAST.
OpenFAST input file heading:
FAST Certification Test #18: NREL 5.0 MW Baseline Wind Turbine (Onshore)

Running ElastoDyn.
Nodal outputs section of ElastoDyn input file not found or improperly formatted.
Running AeroDyn.
AD15 Nodal Outputs: Nodal output section of AeroDyn input file not found or improperly formatted.
Skipping nodal outputs.
Running InflowWind.
Running ServoDyn.
Running ServoDyn Interface for Bladed Controllers (using Intel Visual Fortran for Windows, ).
Using legacy Bladed DLL interface.
Running OpenFAST.
OpenFAST input file heading:
FAST Certification Test #18: NREL 5.0 MW Baseline Wind Turbine (Onshore)

Running ElastoDyn.
Nodal outputs section of ElastoDyn input file not found or improperly formatted.
Running AeroDyn.
AD15 Nodal Outputs: Nodal output section of AeroDyn input file not found or improperly formatted.
Skipping nodal outputs.
Running InflowWind.
Running ServoDyn.
Running ServoDyn Interface for Bladed Controllers (using Intel Visual Fortran for Windows, ).
Using legacy Bladed DLL interface.
Running OpenFAST.
OpenFAST input file heading:
FAST Certification Test #18: NREL 5.0 MW Baseline Wind Turbine (Onshore)

Running ElastoDyn.
Nodal outputs section of ElastoDyn input file not found or improperly formatted.
Running AeroDyn.
AD15 Nodal Outputs: Nodal output section of AeroDyn input file not found or improperly formatted.
Skipping nodal outputs.
Running InflowWind.
Running ServoDyn.
Running ServoDyn Interface for Bladed Controllers (using Intel Visual Fortran for Windows, ).
Using legacy Bladed DLL interface.
from_sc: 1.000000 2.000000 0.0000000E+00 0.0000000E+00
forrtl: severe (170): Program Exception - stack overflow
Image PC Routine Line Source
DISCON_T1.dll 00007FFE0D9D6D88 Unknown Unknown Unknown
DISCON_T1.dll 00007FFE0D971C76 Unknown Unknown Unknown
FAST.Farm_x64.exe 00007FF6E75C287F Unknown Unknown Unknown
FAST.Farm_x64.exe 00007FF6E75C3A5D Unknown Unknown Unknown
FAST.Farm_x64.exe 00007FF6E773DD3F Unknown Unknown Unknown
FAST.Farm_x64.exe 00007FF6E6F07356 Unknown Unknown Unknown
FAST.Farm_x64.exe 00007FF6E6A9D638 Unknown Unknown Unknown
FAST.Farm_x64.exe 00007FF6E684843F Unknown Unknown Unknown
FAST.Farm_x64.exe 00007FF6E69FC9CC Unknown Unknown Unknown
FAST.Farm_x64.exe 00007FF6E66E147C Unknown Unknown Unknown
FAST.Farm_x64.exe 00007FF6E919BE2E Unknown Unknown Unknown
FAST.Farm_x64.exe 00007FF6E96C4914 Unknown Unknown Unknown
KERNEL32.DLL 00007FFE4B297C24 Unknown Unknown Unknown
ntdll.dll 00007FFE4CE8D721 Unknown Unknown Unknown

[/code]

Dear Liye.Zhao,

Well, it appears that FAST.Farm is crashing when the individual wind turbine controller is called. The sample I provided in my post dated Mar 18, 2021 (updated on May 10, 2021) above is a working example. To run this super controller example, all you should need to do is:

  • Compile the turbine-level (DISCON_SC.f90) and the farm-level (sc_dll.f90) controllers into .dll files (or .so files for Mac/Linux) and make three copies of the DISCON (each named uniquely), one for each wind turbine;
  • Use the TSinflow FAST.Farm example from the r-test (github.com/OpenFAST/r-test/tree … m/TSinflow) and change UseSC to True in the FAST.Farm primary input file (TSinflow.fstf);
  • Set FAST.Farm input SC_FileName from the primary input file (TSinflow.fstf) to the SC_DLL.dll (or .so) compiled in the first step; and
  • Set ServoDyn input DLL_FileName from the ServoDyn input file for each wind turbine (NRELOffshrBsline5MW_Onshore_ServoDyn_WT1.dat for turbine 1; likewise for turbines 2 and 3) to the DISCON.dll (or .so, named uniquely for that turbine) compiled in the first step.
  • Set ServoDyn inputs YCMode = 5 and TYCOn = 0.0 s to accept yaw-rate commands from the controll DLL and ensure that you have YawDOF = True in ElastoDyn.

Is this the process you have followed?

Best regards,

1 Like

Dear Jason,

When running FAST.Farm,I used 5MW Spar wind Turbine model sucessfully.But after I changed the coordinates of three wind turbines,the example can not running and there is no error message.This is the running interface.


And this is my .fst file.

I changed the distance between wind turbines to 6D,I don’t know the specific reason for this result so I hope to get your help.
Many thanks!

Best regards,

RuoNan.Zhu

Dear RuoNan.Zhu,

It is not clear to me what the problem is. The high-resolution domains appear to be centered around each wind turbine and the low-resolution domain looks sufficient as well. Unfortunately, the actual error causing the abort appears to be missing because there are so many prior warnings that are taking up space in the WRITE statement.

The warnings about the centers of wake planes passing the lowest-most Z boundary, which is 5 m above MSL, are a bit peculiar considering the warnings appear so soon into the simulation. What do the time series of the wind turbines look like before the simulation aborts?

Can you run one of the OpenFAST models in standalone OpenFAST (uncoupled from FAST.Farm) without error?

Best regards,

Dear Jason,

I am a PHD student in Zhejiang University, China. I am interested in wake steering and its impact on wind farm power, and I am studying FAST.Farm. Recently, I repeated the same case presented in the paper Simulation comparison of wake mitigation control strategies for a two-turbine case, which contained a simulation of two 5-MW turbines, 7 rotor diameters (7D) apart, aligned in a turbulent inflow. The wind speed is 8 m/s with constant wind direction, and the simulations lasted for 600s, shown in Fig.1. It is supposed to improve the total power by misaligning the yaw angle of the front turbine (T1) with the wind direction, but simulation results based on FAST.Farm shown in Fig.2, seemed that wake steering brought power reduction with default wake dynamics calibration parameters. However, when I changed the calibrated parameter C_Meander from 1.9 (default) to 1.5, the simulation results showed yaw misalignment of T1 could bring an increase of total power in some cases in Fig.3, which are similar to the results based on SOWFA (shown in Fig.4) presented in the paper above. I would be very appreciative if you can give me any hint on why this happens. And I wonder whether it is reasonable to change the calibrated parameter for the wake meandering as I did, if I want to study wake steering optimization further. Thank you in advance.

Best regards,
Jili


Dear Jili,

Good question. This is a study I’ve wanted us to perform at NREL, but we haven’t done so yet. I’m quite interested in your results.

It looks like reducing C_Meander gives results similar to the SOWFA results, except at the opposite yaw angles. Is the yaw angle convention the same between the paper you reference and your FAST.Farm results?

Normally I’d recommending modifying C_Meander different from its default value only when calibrating FAST.Farm against high-fidelity solutions (like SOWFA) or known measurements, e.g, based on knowledge of the actual meandering wake centerline. Unfortunately, I don’t see that the wake centerline is reported in the paper you reference, although you could extract it from the SOWFA results if you had those. Other FAST.Farm input parameters that could impact these results are those associated with the horizontal wake deflection correction (C_HWkDfl_O, etc.). The existing DEFAULT values of C_Meander, C_HWkDfl_O, etc. were derived for the NREL 5-MW baseline turbine based on output from SOWFA. So, it may be hard to justify changing C_Meander, C_HWkDfl_O, etc. in you case. Just FYI: reducing C_Meander will result in more wake meandering.

One problem with the existing wake steering solution in FAST.Farm is that while the wake deflection and meandering are captured by FAST.Farm, the curl of the wake induced by the skewed flow is not currently captured by FAST.Farm. That said, we are currently working to implement a curled wake model in FAST.Farm based on an extension of the curled wake formulation developed by Luis 'Tony" Martínez-Tossas et al. I’m hopeful that this new curled wake model in FAST.Farm will improve the results of FAST.Farm for wake-steering applications. We expect to release this upgrade in next month.

Best regards,

1 Like

Dear Jason:
Thank you very much! The problem has been solved, this time I compiled and used Discon_sc.f90 ,then then renamed it Discon_T1.dll…, it worked very well. I read discon_sc.f90 carefully and found the input from_SC_glob instead of from_SCglob.

Another question is what does the superController.f90 file do? I checked the manual. I couldn’t find it. Thank you very much again!

Liye
Best regard!