<p>As far as I have understood, you aim to develop a framework to capture the hardness of combinatorial problems in 3D.
However, there are major problems in your question.</p>
<p>Your first sentence lacks a couple of technical definitions:</p>
<blockquote>
<p>For a specific f(), I'm defining a term 'complexity', estimating how
difficult is the given function to optimize.</p>
</blockquote>
<p>First, and the most important of all, you should have a well defined <strong>complexity</strong> measure in order to adapt the term.
Then, another sentence makes your question even more complicated:</p>
<blockquote>
<p>If it's easy to achieve an output of 1 through any random input, then
you have a low complexity space.</p>
</blockquote>
<p>Here, you need to have a clear definition of <strong>easy</strong>. Is it in terms of computational complexity? If so, how do you measure the input size?</p>
<p>After this sentence, I am honestly lost:</p>
<blockquote>
<p>Complexity measured as volume enclosed between the xy-plane and the
z-hyperplane seems valuable, but it alone does not work, because
increasing volume at z=0.8 depth is 'worth more' than the same amount
increased at 0.2 depth (in terms of optimizing for z=1). It's not just
the z=1 region that is important as 'success', but also where z=0.9,
z=0.8, etc. proportionally.</p>
</blockquote>
<p>What does it mean to worth more? What is increasing, and what is decreasing? What are yoou trying to optimize?</p>
<p>All in all, although I could not understand your question well enough, I would go ahead and say that there are different ways to measure &quot;complexity&quot; in different dimensions, unless you invent a brand new system to represent the coordinates.</p>

CC BY-SA 4.0
2020-10-22T16:25:33.830Z
Sorry you didn't get much from the post, I'll try to explain. (1) Of course the post lacks a good definition for 'complexity', that is the entire goal of the post, to define the term computationally. (2) 'Easy' does need to be defined too, and I start in the post to look at 'ease' as how much 'volume' of the solution space leads towards or is at a depth where z=1 (ie. a global minimum has been found' (maximum actually). What do you mean by 'measure the input size'?
user2827214
CC BY-SA 4.0
2020-10-22T21:25:18.193Z
Complexity is a broadly used term, which usually refers to the computational complexity. To put very roughly, computational complexity is measured by the resource usage w.r.t. the input size. So, if you are to mention complexity, first you need to tell with respect to what.
padawan
CC BY-SA 4.0
2020-10-21T07:32:00.113Z
2020-10-21T07:32:00.113Z
padawan
<p><strong>Edit:</strong> 'Fitness landscape analysis' was mentioned as a relevant measure. If you're going to downvote the post, at least leave a comment what is wrong.</p>
<p>For a specific f(), I'm defining a term 'complexity', estimating how difficult is the given function to optimize.
I attempted a solution in low dimension, but I might not be on the right track to generalize to n-dimn.
This concept probably has a name and a better existing approximation, but here's what I have:</p>
<p>f(x) has input values bound [0, 5], x = [x1, x2, x3, x4...] (n-dimn),
and f() outputs a single continuous value for 'success', bound [0, 1]</p>
<p><strong>Example:</strong></p>
<p>For input [x1, x2], calculate f(x) = y,
and then relabel (x1, x2, y) as (x, y, z) for the plots below.</p>
<p>If it's easy to achieve an output of 1 through any random input, then you have a low complexity space.</p>
<p>An example f() space, where all input values result in z=1 (low complexity):</p>
<p><a href="https://i.sstatic.net/B5QSh.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/B5QSh.png" alt="low complexity" /></a></p>
<p>An example f() space, where only one input value results in z=1 (high complexity):</p>
<p><a href="https://i.sstatic.net/MHwUg.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/MHwUg.png" alt="high complexity" /></a></p>
<p>Complexity measured as volume enclosed between the xy-plane and the z-hyperplane seems valuable, but it alone does not work, because increasing volume at z=0.8 depth is 'worth more' than the same amount increased at 0.2 depth (in terms of optimizing for z=1).
It's not just the z=1 region that is important as 'success', but also where z=0.9, z=0.8, etc. proportionally.</p>
<p>So what I've come up with so far is to compute a grid of inputs, and get their output values:
i.e.
f([0, 0])=0.0
f([0, 1])=0.3
f([0, 2])=0.2
...
then plot those to approximate the z-hyperplane.
If I sum all the sample's z-values (0, .3, .2...) (and as the number of samples on the grid increases),
it gives a nice sort of depth-weighted volume estimate.</p>
<p><a href="https://i.sstatic.net/767HV.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/767HV.png" alt="grid sample" /></a></p>
<p>There's a problem that local minima can cause increased volume (lower complexity),
yet lead away and make it more difficult to navigate toward any deeper / global min's (higher complexity).
(Weighted volume might handle this, but I'm unsure)</p>
<p>Example f() space where both have the same volume (picture's not exact, but you get it right? and I rotated axes, sry):</p>
<p><a href="https://i.sstatic.net/Wa8Pz.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/Wa8Pz.png" alt="local min" /></a></p>
<p>How can I incorporate that factor, that some points on the function increase volume, but the addition of that volume contributes less than if the volume was adjacent to a deeper space (in a similar function, ex. the f() on the right, above)?
It seems like the critical feature that distinguishes those two hyperplanes is that the sign of the slope flips,
where the negative slope leads into a local min, away from the global min,
and the more frequently the sign flips, the harder the function will be to optimize.</p>
<p><a href="https://i.sstatic.net/Zys8i.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/Zys8i.png" alt="sign change" /></a></p>
<p>If I iterate the grid rows and cols, and calculate the number of slope sign changes, that might be useful,
or there might be a way to use trig to project a line and see what depth it intersects the hyperplane,
but this is where I realized I need help.</p>
<p>My original idea was to define complexity as how resistant are the output values to fluctuations in the input values, given a specific input.
So I have a decent estimate with my 'weighted-volume' calculation, but it's still lacking.</p>
<p><strong>(1) Do you recognize the 'complexity' concept as another existing term?</strong></p>
<pre><code>I found 'fitness landscape analysis' in evolutionary optimization
</code></pre>
<p><strong>(2) If not, can I improve beyond 'weighted-volume'?</strong></p>
<p><strong>(3) Will this work for higher dimensions?</strong></p>

<cc.complexity-theory><optimization><machine-learning><computational-geometry><high-dimensional-geometry>
How to calculate complexity in a high dimensional space?
user2827214
# How to calculate complexity in a high dimensional space?

(Asked by: username_0 on 2020-10-20)

Edit: 'Fitness landscape analysis' was mentioned as a relevant measure. If you're going to downvote the post, at least leave a comment what is wrong.
For a specific f(), I'm defining a term 'complexity', estimating how difficult is the given function to optimize.
I attempted a solution in low dimension, but I might not be on the right track to generalize to n-dimn.
This concept probably has a name and a better existing approximation, but here's what I have:
f(x) has input values bound [0, 5], x = [x1, x2, x3, x4...] (n-dimn),
and f() outputs a single continuous value for 'success', bound [0, 1]
Example:
For input [x1, x2], calculate f(x) = y,
and then relabel (x1, x2, y) as (x, y, z) for the plots below.
If it's easy to achieve an output of 1 through any random input, then you have a low complexity space.
An example f() space, where all input values result in z=1 (low complexity):

An example f() space, where only one input value results in z=1 (high complexity):

Complexity measured as volume enclosed between the xy-plane and the z-hyperplane seems valuable, but it alone does not work, because increasing volume at z=0.8 depth is 'worth more' than the same amount increased at 0.2 depth (in terms of optimizing for z=1).
It's not just the z=1 region that is important as 'success', but also where z=0.9, z=0.8, etc. proportionally.
So what I've come up with so far is to compute a grid of inputs, and get their output values:
i.e.
f([0, 0])=0.0
f([0, 1])=0.3
f([0, 2])=0.2
...
then plot those to approximate the z-hyperplane.
If I sum all the sample's z-values (0, .3, .2...) (and as the number of samples on the grid increases),
it gives a nice sort of depth-weighted volume estimate.

There's a problem that local minima can cause increased volume (lower complexity),
yet lead away and make it more difficult to navigate toward any deeper / global min's (higher complexity).
(Weighted volume might handle this, but I'm unsure)
Example f() space where both have the same volume (picture's not exact, but you get it right? and I rotated axes, sry):

How can I incorporate that factor, that some points on the function increase volume, but the addition of that volume contributes less than if the volume was adjacent to a deeper space (in a similar function, ex. the f() on the right, above)?
It seems like the critical feature that distinguishes those two hyperplanes is that the sign of the slope flips,
where the negative slope leads into a local min, away from the global min,
and the more frequently the sign flips, the harder the function will be to optimize.

If I iterate the grid rows and cols, and calculate the number of slope sign changes, that might be useful,
or there might be a way to use trig to project a line and see what depth it intersects the hyperplane,
but this is where I realized I need help.
My original idea was to define complexity as how resistant are the output values to fluctuations in the input values, given a specific input.
So I have a decent estimate with my 'weighted-volume' calculation, but it's still lacking.
(1) Do you recognize the 'complexity' concept as another existing term?
I found 'fitness landscape analysis' in evolutionary optimization

(2) If not, can I improve beyond 'weighted-volume'?
(3) Will this work for higher dimensions?

**Tags:** cc.complexity-theory, optimization, machine-learning, computational-geometry, high-dimensional-geometry

---

## 1 answers

### Answer by username_1 on 2020-10-21. Score: 1

As far as I have understood, you aim to develop a framework to capture the hardness of combinatorial problems in 3D.
However, there are major problems in your question.

Your first sentence lacks a couple of technical definitions:

> For a specific f(), I'm defining a term 'complexity', estimating how
> difficult is the given function to optimize.

First, and the most important of all, you should have a well defined **complexity** measure in order to adapt the term.
Then, another sentence makes your question even more complicated:

> If it's easy to achieve an output of 1 through any random input, then
> you have a low complexity space.

Here, you need to have a clear definition of **easy**. Is it in terms of computational complexity? If so, how do you measure the input size?

After this sentence, I am honestly lost:

> Complexity measured as volume enclosed between the xy-plane and the
> z-hyperplane seems valuable, but it alone does not work, because
> increasing volume at z=0.8 depth is 'worth more' than the same amount
> increased at 0.2 depth (in terms of optimizing for z=1). It's not just
> the z=1 region that is important as 'success', but also where z=0.9,
> z=0.8, etc. proportionally.

What does it mean to worth more? What is increasing, and what is decreasing? What are yoou trying to optimize?

All in all, although I could not understand your question well enough, I would go ahead and say that there are different ways to measure "complexity" in different dimensions, unless you invent a brand new system to represent the coordinates.

> **Comments:**
> **username_0**: Sorry you didn't get much from the post, I'll try to explain. (1) Of course the post lacks a good definition for 'complexity', that is the entire goal of the post, to define the term computationally. (2) 'Easy' does need to be defined too, and I start in the post to look at 'ease' as how much 'volume' of the solution space leads towards or is at a depth where z=1 (ie. a global minimum has been found' (maximum actually). What do you mean by 'measure the input size'?  
> **username_1**: Complexity is a broadly used term, which usually refers to the computational complexity. To put very roughly, computational complexity is measured by the resource usage w.r.t. the input size. So, if you are to mention complexity, first you need to tell with respect to what.  

---

