Insights Fixing Things Which Can Go Wrong With Complex Numbers

  • Thread starter Thread starter PAllen
  • Start date Start date
AI Thread Summary
The discussion revolves around correcting the use of logarithmic notation in a document about complex numbers. Participants request replacing "log" with "\log" or "\ln" for clarity and consistency. There are mentions of editing permissions being restored, allowing for these changes to be made collectively. Additionally, a few typographical errors, such as using "principle" instead of "principal," are noted. The conversation highlights the importance of adhering to established conventions in mathematical notation.
Mathematics news on Phys.org
Hi, I know you worked a lot to write it, but can you at least replace log with \log everywhere, or ideally with \ln? Thank you!
 
dextercioby said:
Hi, I know you worked a lot to write it, but can you at least replace log with \log everywhere, or ideally with \ln? Thank you!
If Greg restores ability to edit, I am willing to do this within all latex brackets. Where I just refer to log as text, I would rather not, but could be persuaded.

It would have been much easier to address this had you raised it during the period I had it up as "request for review" in the advisor lounge.
 
Last edited:
I'll wait to see if any other requests for improvement come in, so I can do all at once.
 
  • Like
Likes Greg Bernhardt
dextercioby said:
Hi, I know you worked a lot to write it, but can you at least replace log with \log everywhere, or ideally with \ln? Thank you!
Isn't the complex logarithm traditionally denoted ##\log##, not ##\ln##?

PAllen said:
I'll wait to see if any other requests for improvement come in, so I can do all at once.
I noticed in a couple of places you used principle where you meant principal.
 
  • Like
Likes jim mcnamara
vela said:
Isn't the complex logarithm traditionally denoted ##\log##, not ##\ln##?


I noticed in a couple of places you used principle where you meant principal.
Thanks!
 
vela said:
Isn't the complex logarithm traditionally denoted ##\log##, not ##\ln##?


I noticed in a couple of places you used principle where you meant principal.
It depends on what you consider "tradition". The official use in the US (which is not my country, btw) is the NIST one:

https://dlmf.nist.gov/4.2
 
let’s tie up the delta thread, the branch-surface complex thread, and the SSH/lattice operator thread into one deep-math lattice:




1. Core unification:​


  • Dirac/Kronecker delta: both are evaluation functionals defined relative to a measure.

    δx0(μ)(φ)=φ(x0).\delta^{(\mu)}_{x_0}(\varphi) = \varphi(x_0).δx0(μ)(φ)=φ(x0).
  • SSH annihilation operators: are discrete delta-like objects in Fock space; they “pick out” occupancy at a site.
  • Complex multivaluedness: exponentiation and logarithm are not single-valued on C\mathbb{C}C; you need the covering surface ZZZ. That sheet index acts like a discrete Kronecker delta tagging which branch you’re on.

So: delta = identity of convolution; branch index = hidden discrete label; lattice operators = concrete delta-action on Hilbert space.




2. A single mathematical frame​


Let’s write a hybrid object:

Δ(μ,Z)(x,k):=δx(μ)⊗δk(Z),\Delta^{(\mu,Z)}(x,k) := \delta^{(\mu)}_{x} \otimes \delta^{(\mathbb{Z})}_{k},Δ(μ,Z)(x,k):=δx(μ)⊗δk(Z),
where


  • xxx is your continuum variable,
  • μ\muμ is the measure (Lebesgue, counting, spectral),
  • kkk is the branch index (sheet of log/exponential),
  • δk(Z)\delta^{(\mathbb{Z})}_kδk(Z) is the Kronecker delta tagging branches.

This Δ(μ,Z)\Delta^{(\mu,Z)}Δ(μ,Z) acts as a branch-aware delta functional.




3. Tie-in formulas​


  • SSH jump terms (Lindblad):

    a1ρa1†=Δ1(μ)⋅ρ⋅Δ1(μ),a_1\rho a_1^\dagger = \Delta^{(\mu)}_{1} \cdot \rho \cdot \Delta^{(\mu)}_{1},a1ρa1†=Δ1(μ)⋅ρ⋅Δ1(μ),
    i.e. a “delta projector” at site 1.
  • Complex log law fix:
    Instead of

    log⁡(za)=alog⁡z,\log(z^a) = a \log z,log(za)=alogz,
    we use

    log⁡(za)=alog⁡z+2πi k,k∈Z.\log(z^a) = a\log z + 2\pi i\,k,\qquad k\in \mathbb{Z}.log(za)=alogz+2πik,k∈Z.
    Here kkk is exactly the Kronecker-delta branch label.
  • Distributional bridge:

    δ(f(x))=∑xk: f(xk)=0δ(x−xk)∣f′(xk)∣\delta(f(x)) = \sum_{x_k:\ f(x_k)=0}\frac{\delta(x-x_k)}{|f'(x_k)|}δ(f(x))=xk: f(xk)=0∑∣f′(xk)∣δ(x−xk)
    generalizes naturally to

    δ(f(x),k)=∑(xk,m)δ(x−xk) δk,m∣f′(xk)∣.\delta(f(x), k) = \sum_{(x_k,m)} \frac{\delta(x-x_k)\,\delta_{k,m}}{|f'(x_k)|}.δ(f(x),k)=(xk,m)∑∣f′(xk)∣δ(x−xk)δk,m.
    (branch-resolved zeros).



4. Deep-math proposition (new, falsifiable)​


Branch-aware Lindblad–Delta Hypothesis:
Every time a quantum system with dissipation involves a multivalued complex map (e.g., Green’s function poles, logarithmic time evolution, fractional powers), you can replace the naïve δ\deltaδ by a branch-aware Δ(μ,Z)\Delta^{(\mu,Z)}Δ(μ,Z).


Prediction: this removes apparent “violations” of sum rules in open-system SSH simulations where the log branch cut otherwise causes normalization mismatches.


Test: numerically evolve correlation matrix with and without branch-aware bookkeeping; check whether Tr ρ(t)=1\mathrm{Tr}\,\rho(t)=1Trρ(t)=1 survives longer in the branch-aware scheme. If yes → the theory has bite.




5. The tie-up picture​


  • Delta: localizes.
  • Branch index: remembers winding history.
  • Annihilation operators: implement discrete deltas on Hilbert space.
  • SSH Hamiltonian: alternates couplings, which is exactly a two-delta modulation (odd vs even bonds).
  • Complex log fixes: require carrying a discrete delta label (branch).

So in the deepest sense: all three stories (Dirac, branch cuts, SSH jumps) are about not losing the discrete delta labels that live underneath the smooth continuum.




Louis — do you want me to crystallize this into a one-page “Branch-Delta Lattice” card (equations only + a little diagram of continuum line × branch sheet × Fock sites),
 
  • #10
Lox99 said:
let’s tie up the delta thread, the branch-surface complex thread, and the SSH/lattice operator thread into one deep-math lattice:
Your math is unreadable; please edit your post.
 
  • #11
Also, this is clearly discussion of an idea for a new insight. It doesn't really belong in one on feedback to an existing one.
 
  • #12
@Lox99 Is this AI generated text?
 

Similar threads

Replies
5
Views
200
3
Replies
108
Views
10K
Replies
3
Views
2K
Replies
0
Views
2K
Replies
25
Views
4K
Replies
13
Views
4K
Replies
4
Views
3K
Replies
0
Views
2K
Back
Top