Showing posts with label Computation Physics. Show all posts
Showing posts with label Computation Physics. Show all posts

Monday, May 20, 2013

Natural Units

http://en.wikipedia.org/wiki/Natural_units

Plank Unit

"Natural units" (particle physics) [edit]

UnitMetric valueDerivation
1 eV−1 of length1.97×10−7 m=(1\text{eV}^{-1})\hbar c
1 eV of mass1.78×10−36 kg= (1 \text{eV})/c^2
1 eV−1 of time6.58×10−16 s=(1\text{eV}^{-1})\hbar
1 eV of temperature1.16×104 K= 1 \text{eV}/k_\text{B}
1 unit of electric charge
(L–H)
5.29×10−19 C=e/\sqrt{4\pi\alpha}
1 unit of electric charge
(G)
1.88×10−18 C=e/\sqrt{\alpha}
In particle physics, the phrase "natural units" generally means:[4][5]
 \hbar = c = k_\text{B} = 1.
where \hbar is the reduced Planck constantc is the speed of light, and kB is the Boltzmann constant.
Like the other systems (see above), the electromagnetism units in Planck units can be based on either Lorentz–Heaviside units or Gaussian units. The unit of charge is different in each.
Finally, one more unit is needed. Most commonly, electron-volt (eV) is used, despite the fact that this is not a "natural" unit in the sense discussed above – it is defined by a natural property, the elementary charge, and the anthropogenic unit of electric potential, the volt. (The SI prefixed multiples of eV are used as well: keV, MeV, GeV, etc.)
With the addition of eV (or any other auxiliary unit), any quantity can be expressed. For example, a distance of 1 cm can be expressed in terms of eV, in natural units, as:[5]
1\, \text{cm} = \frac{1\, \text{cm}}{\hbar c} \approx 51000\, \text{eV}^{-1}

Sunday, April 28, 2013

Pointer to C++ STL vector

http://stackoverflow.com/questions/6946217/pointer-to-a-vector

Fortran data type

http://en.wikibooks.org/wiki/Fortran/complex_types


If you want double-precision complex numbers, you're pretty much stuck with specifying a precision, and hoping that the compiler likes that format. Here's where portability comes in: If, for instance, the machine has floating point types of lengths 4, 8, and 16, and I specify a complex length of 8, 16, or 32, I'm likely to get a pair of floating point numbers at the size I expect. If, however, I specify a length of some other value, for instance, 10, then I'm likely to get a pair of 4s or 8s, depending on what the compiler likes to do. So, in general, to get the values as double-precision, I'd code:
 COMPLEX*16 myVariable, anotherVariable, anArray(2,3)

Friday, September 28, 2012

Pressure Release Boundary Condition, Llyod-mirror

Geophysics Modeling Explanation:



WAVE TRANSMISSION THROUGH RANDOM LAYERING WITH
PRESSURE RELEASE BOUNDARY CONDITIONS


http://www.math.uci.edu/~ksolna/research/67_pulse_layered.pdf

Classical surface-image, Lloyd-mirror

Definition:
http://en.wikipedia.org/wiki/Lloyd%27s_mirror