Change MPI related arguments to global to reduced the number of arguments in many calls.

[lmdiazangulo]

Considering this example of code in observation.F90

       do ii = 1, sgg%NumberRequest
          if (SGG%Observation(ii)%FreqDomain) then
            call init_frequency_output(sgg%observation(ii), output(ii), sgg%dt, layoutnumber, size, niapapostprocess)
          end if !del freqdomain
        end do

The layoutnumber and size variables are related to MPI processes?

If that is the case. Would it be better to change them to global singleton variables to reduce the number of arguments that are always passed?

[lmdiazangulo]

@Alberto-o @adrianarce-elemwave what do you think?

[Alberto-o]

The layoutnumber and size variables are related to MPI processes? Yes, I'm pretty sure they refer to the current layer and the total number of MPI layers. I see that most of the times they are only used as an argument to function stoponerror (but not exclusively).

If defined as singleton global, they would be available not just for this module, for the whole program?

[lmdiazangulo]

The layoutnumber and size variables are related to MPI processes? Yes, I'm pretty sure they refer to the current layer and the total number of MPI layers. I see that most of the times they are only used as an argument to function stoponerror (but not exclusively).

If defined as singleton global, they would be available not just for this module, for the whole program?

Yes, they would be available for the whole program. The could live in a module related with MPI and initialized to some special value if MPI is not initialize. MPI has some global variables which are unique for the specific process. I think this is the case with these two variables.