Where is the epipole if one camera center is not in view of the other?

In the book multiple view geometry, the epipole is defined as follows:

The epipole is the point of intersection of the line joining the camera centres (the baseline) with the image plane. Equivalently, the epipole is the image in one view of the camera centre of the other view. It is also the vanishing point of the baseline (translation) direction.

The image of one camera center could easily not be in view of another camera center without the cameras being parallel. So, in this case, the line connecting the camera centers would not intersect at least one of the image planes. So, where is the epipole in this case?

Don’t send notification to Notification Center on Apple Watch

Is it possible to restrict certain app notifications from going to the Notification Center on Apple Watch?

One use case: I’d like to receive phone calls on the watch, but I don’t want those unanswered calls to end up in Notification Center.

Another: I’d like to get notified of calendar updates, but I don’t want them to end up in Notification Center.

How can I move the character to the center of the screen when the user clicks with the primary mouse button?

I am a newbie at this and I’m just trying to learn how to do different things. I am wanting to move a character sprite in a horizontal line, toward the center of the screen when the primary mouse button is detected and then it moves back to the edge of the screen when no input is detected. Any help would be greatly appreciated.

Local central limit theorem far from the center

Let $ X_i$ be a sequence of iid random variables, $ E [X] = 0$ , $ E [X^2] = 1$ and $ E [|X|^k] < \infty$ for some $ k \ge 3$ . Classical local CLT says that the density function $ f_n$ of $ \frac1{\sqrt n}\sum_1^n X_i$ satisfies that $ $ f_n(x) – \phi(x)\left(1 + \sum_{j=1}^{k-2} n^{-\frac j2}P_j(x)\right) = o\left(n^{-\frac{k-2}2}\right), \quad \phi(x) = \frac1{\sqrt{2\pi}}e^{-\frac{x^2}2} $ $ where $ P_j$ is some $ (j + 2)$ -order polynomial, and the RHS is uniformly small for $ x \in R$ .

This gives us very good estimate for constant $ x$ . My question is that can we get a similar expansion equation for $ f_n(\sqrt nx)$ ? Since $ \phi(\sqrt nx)$ decays faster than any polynomial order in $ n$ , we can not apply the local CLT directly.

Remark: I consider this in order to estimating the following expression for $ x \not= 0$ and $ y$ : $ $ \frac1{f_n(\sqrt nx)}f_{n-1}\left(\frac{nx + y}{\sqrt{n-1}}\right), \quad n \text{ sufficiently large}. $ $ When $ x = 0$ by local CLT this is bounded by $ 1 + C(1+y^2)/n + o(1/n)$ . If $ x \not= 0$ , I expect the upper bound $ $ \exp\left\{-\frac{x^2}2 – xy\right\}\left[1 + \frac{C(x^2 + y^2)}n + o\left(\frac1n\right)\right]. $ $

What ASCII character to use for “align center”?

If I use < to represent the setting “align left” and > to represent the setting “align right” what symbol should I use for “align center”? Is there any de facto standard for this? The symbol has to be an ASCII character the user can type on a US keyboard layout.

Context

I am working on the command line interface of a console application for Unix-like operating systems that can output pseudographical tables, like so:

┌─────┬─────┬────────┬─────┐ │ PID │ TTY │  TIME  │ CMD │ ├─────┼─────┼────────┼─────┤ │ 8580│pts/1│00:00:00│  ps │ ├─────┼─────┼────────┼─────┤ │28075│pts/1│00:00:01│ zsh │ └─────┴─────┴────────┴─────┘ 

The application can be told to align the text in each column left, right or center. To make it do that the user gives it the command line option -align LIST where LIST is a list of words “left”, “right” or “center” where each word corresponds to one column, e.g., -align 'left left right center'.

I found that having to write each word in full takes too much effort. I intend to introduce l (a small L), r and c as shortcuts (which has precedent in LaTeX) but I also want to offer another, more graphical set of shortcut characters that would be easier to understand at a glace, say, when reading a shell script. Since using <, > for “left” and “right” respectively seems inevitable I am looking for the third unknown symbol to go with those two.

The logic behind the switchers placement in the iOS Control Center

The iOS Control Center contains two rows of buttons at the top and bottom of the area. The previous implementation of it made more sense to me, as the top buttons were switchers, and the bottom buttons were mostly launchers (except for the flashlight, which feels out of place).

image
(source: wikimedia.org)

The most recent update introducing the Night Shift feature brought a new button to the Control Center. It’s now located in the middle of the bottom row and is responsible for toggling that feature on/off.

image

I can see how the Flashlight could have been a one-time trade-off because on the other hand, the interaction span with that particular feature is supposed to be short: you launch it, quickly use it, and get back to whatever you were doing (just like with the Camera, Calculator or Timer).

But now I don’t understand the logic behind those placement decisions completely. The Night Shift button is definitely a switcher, it can stay on for a long period of time, and it does feel like it belongs to the area where most of the switchers are. I do realise that the area will become too crowded, but then again, it is possible to have two rows of icons in there, with the secondary ones grouped in a collapsible/expandable area – just like the one that let’s you act on a banner notification (e.g. reply to a text message). That would also make it possible to include the switches for the Low Power Mode, Cellular Data and Auto Brightness in that quick access area, this way making it even more feature-rich.

Before you tell me this actually belongs to Apple’s feedback website, let me finally ask my question: is there any logic behind this placement? It just doesn’t feel right, consistent or predictable. Yet I’m sure they know what they’re doing, which makes me wonder if I’m missing something.

I did a search before asking to see if this is not going to be a duplicate.