J
Joe Gwinn
Guest
On Wed, 4 Jan 2023 16:08:37 +0000, Martin Brown
<\'\'\'newspam\'\'\'@nonad.co.uk> wrote:
Yes, but if I recall we called them Assertions:
..<https://en.wikipedia.org/wiki/Assertion_(software_development)>
Software also has Invariants, but I don\'t know that either one came
from the Physics world.
..<https://en.wikipedia.org/wiki/Invariant_(mathematics)#Invariants_in_computer_science>
The main difference in software seems to be that assertions are
logical statements about the value of a single variable, while
Invariants apply an assertion to the result of a specified function.
One kind of assertion was visual - coplot a 2D plot of something, plus
a circle, and visually verify concentricity. The eye is _very_ good
at this, so it was a very robust and sensitive test.
I for one used them heavily, with some being used in operation, not
just development. This was done in runtime code, not as a property of
the programming language and/or compiler.
Joe Gwinn
<\'\'\'newspam\'\'\'@nonad.co.uk> wrote:
On 04/01/2023 14:54, bitrex wrote:
On 1/4/2023 9:52 AM, bitrex wrote:
On 1/3/2023 7:30 PM, Phil Hobbs wrote:
I agree that knowing the fundamentals cold is very important.
However, (a) physics isn\'t for everyone, by a long chalk; and (b)
there\'s a glorious intellectual heritage in engineering, so calling
it \'vocational training\' is pejorative.
Cheers
Phil \"Intermediate energy state\" Hobbs
Advanced engineering mathematics:
https://www.ebay.com/itm/194964206310
Which is pretty advanced, I don\'t know how many BS-type EEs know about
the orthogonality of Bessel functions, or regularly use contour
integration for anything.
I once used contour integration to obtain a fringe field correction on a
mass spectrometer magnet. The objective was to take out the first order
aberrations and make the focal plane orthogonal to the optic axis.
It was one of the first electromagnetic optics codes where the magnitude
of the predicted voltages on electrodes was sometime right. Prior to
that you were lucky if it had the right sign! The original code came off
a mainframe and was intended for designing atom smashers. A listing
arrived at the company from academia with my new boss.
Physics was mainly into Chebyshev polynomials for solving wavefunction
equations since it housed one of the world experts in the field.
But not as advanced as \"Advanced Mathematical Methods for Scientists &
Engineers\", which is largely about perturbation methods, boundary
layer theory, and WKB approximations. Sounds fun I guess, I just got a
used copy from Amazon for $8
I would expect stuff like the WKB approximation is regularly used more
in optics design than in circuit design, though.
A bit like Green\'s function I\'m inclined to think that WKB is seldom
used at all now that we have very fast raytracers on the desktop PC. It
may still be taught at undergraduate level today but mainly to weed out
those that are not going to make it as a theoretical physicist (which is
where it was used back in my day as an undergraduate).
Padé rational approximation methods are undergoing something of a
Renaissance. Things go in cycles. I keep waiting for Clifford Algebras
to take off as my supervisor promised they soon would (~2 decades ago).
Things which do have an important place in modern software that is
intended to be provably correct are invariants (borrowed from physics).
Yes, but if I recall we called them Assertions:
..<https://en.wikipedia.org/wiki/Assertion_(software_development)>
Software also has Invariants, but I don\'t know that either one came
from the Physics world.
..<https://en.wikipedia.org/wiki/Invariant_(mathematics)#Invariants_in_computer_science>
The main difference in software seems to be that assertions are
logical statements about the value of a single variable, while
Invariants apply an assertion to the result of a specified function.
One kind of assertion was visual - coplot a 2D plot of something, plus
a circle, and visually verify concentricity. The eye is _very_ good
at this, so it was a very robust and sensitive test.
I for one used them heavily, with some being used in operation, not
just development. This was done in runtime code, not as a property of
the programming language and/or compiler.
Joe Gwinn