Sign upLogin

alchemyst/Skogestad-Python

View on GitHub
Star
Uncertain_MIMO.py

Summary

Maintainability
A
3 hrs
Test Coverage

Function bound_MIMO_wi has 6 arguments (exceeds 4 allowed). Consider refactoring.
Open

def bound_MIMO_wi(w_start, w_end, vec, G, Gp, steps):
Severity: Minor
Found in Uncertain_MIMO.py - About 45 mins to fix

    Function bound_SISO_wi has 6 arguments (exceeds 4 allowed). Consider refactoring.
    Open

    def bound_SISO_wi(w_start, w_end, vec, G, Gp, steps):
    Severity: Minor
    Found in Uncertain_MIMO.py - About 45 mins to fix

      Function weight_calc has 5 arguments (exceeds 4 allowed). Consider refactoring.
      Open

      def weight_calc(w_start, w_end, li, weight_i, steps):
      Severity: Minor
      Found in Uncertain_MIMO.py - About 35 mins to fix

        Function weight_calc_dec has 5 arguments (exceeds 4 allowed). Consider refactoring.
        Open

        def weight_calc_dec(w_start, w_end, li, weight_i, steps):
        Severity: Minor
        Found in Uncertain_MIMO.py - About 35 mins to fix

          Function weight_calc has a Cognitive Complexity of 7 (exceeds 5 allowed). Consider refactoring.
          Open

          def weight_calc(w_start, w_end, li, weight_i, steps):
    """Calculates a simple third-order weight
    Accommodates situations were the weight increases with frequency
    """
          Severity: Minor
          Found in Uncertain_MIMO.py - About 35 mins to fix

          Cognitive Complexity

          Cognitive Complexity is a measure of how difficult a unit of code is to intuitively understand. Unlike Cyclomatic Complexity, which determines how difficult your code will be to test, Cognitive Complexity tells you how difficult your code will be to read and comprehend.

          A method's cognitive complexity is based on a few simple rules:

          • Code is not considered more complex when it uses shorthand that the language provides for collapsing multiple statements into one
          • Code is considered more complex for each "break in the linear flow of the code"
          • Code is considered more complex when "flow breaking structures are nested"

          Further reading

          TODO found
          Open

              # TODO: The following is a list of possible expansions
          Severity: Minor
          Found in Uncertain_MIMO.py by fixme

          Too many blank lines (2)
          Open

              # Calculate sequences to plot all perturbations
          Severity: Minor
          Found in Uncertain_MIMO.py by pep8

          Separate top-level function and class definitions with two blank lines.

          Method definitions inside a class are separated by a single blank
line.

Extra blank lines may be used (sparingly) to separate groups of
related functions.  Blank lines may be omitted between a bunch of
related one-liners (e.g. a set of dummy implementations).

Use blank lines in functions, sparingly, to indicate logical
sections.

Okay: def a():\n    pass\n\n\ndef b():\n    pass
Okay: def a():\n    pass\n\n\nasync def b():\n    pass
Okay: def a():\n    pass\n\n\n# Foo\n# Bar\n\ndef b():\n    pass
Okay: default = 1\nfoo = 1
Okay: classify = 1\nfoo = 1

E301: class Foo:\n    b = 0\n    def bar():\n        pass
E302: def a():\n    pass\n\ndef b(n):\n    pass
E302: def a():\n    pass\n\nasync def b(n):\n    pass
E303: def a():\n    pass\n\n\n\ndef b(n):\n    pass
E303: def a():\n\n\n\n    pass
E304: @decorator\n\ndef a():\n    pass
E305: def a():\n    pass\na()
E306: def a():\n    def b():\n        pass\n    def c():\n        pass

          Too many blank lines (2)
          Open

              #################
          Severity: Minor
          Found in Uncertain_MIMO.py by pep8

          Separate top-level function and class definitions with two blank lines.

          Method definitions inside a class are separated by a single blank
line.

Extra blank lines may be used (sparingly) to separate groups of
related functions.  Blank lines may be omitted between a bunch of
related one-liners (e.g. a set of dummy implementations).

Use blank lines in functions, sparingly, to indicate logical
sections.

Okay: def a():\n    pass\n\n\ndef b():\n    pass
Okay: def a():\n    pass\n\n\nasync def b():\n    pass
Okay: def a():\n    pass\n\n\n# Foo\n# Bar\n\ndef b():\n    pass
Okay: default = 1\nfoo = 1
Okay: classify = 1\nfoo = 1

E301: class Foo:\n    b = 0\n    def bar():\n        pass
E302: def a():\n    pass\n\ndef b(n):\n    pass
E302: def a():\n    pass\n\nasync def b(n):\n    pass
E303: def a():\n    pass\n\n\n\ndef b(n):\n    pass
E303: def a():\n\n\n\n    pass
E304: @decorator\n\ndef a():\n    pass
E305: def a():\n    pass\na()
E306: def a():\n    def b():\n        pass\n    def c():\n        pass

          Too many blank lines (2)
          Open

              # Must change a, b, and c in weight to fit to l_mod
          Severity: Minor
          Found in Uncertain_MIMO.py by pep8

          Separate top-level function and class definitions with two blank lines.

          Method definitions inside a class are separated by a single blank
line.

Extra blank lines may be used (sparingly) to separate groups of
related functions.  Blank lines may be omitted between a bunch of
related one-liners (e.g. a set of dummy implementations).

Use blank lines in functions, sparingly, to indicate logical
sections.

Okay: def a():\n    pass\n\n\ndef b():\n    pass
Okay: def a():\n    pass\n\n\nasync def b():\n    pass
Okay: def a():\n    pass\n\n\n# Foo\n# Bar\n\ndef b():\n    pass
Okay: default = 1\nfoo = 1
Okay: classify = 1\nfoo = 1

E301: class Foo:\n    b = 0\n    def bar():\n        pass
E302: def a():\n    pass\n\ndef b(n):\n    pass
E302: def a():\n    pass\n\nasync def b(n):\n    pass
E303: def a():\n    pass\n\n\n\ndef b(n):\n    pass
E303: def a():\n\n\n\n    pass
E304: @decorator\n\ndef a():\n    pass
E305: def a():\n    pass\na()
E306: def a():\n    def b():\n        pass\n    def c():\n        pass

          There are no issues that match your filters.

          Category
          Status