Idle question: in the days before TeX, when manuscripts like this were hammered out on Remington office typewriters, how did authors handle symbols? In this manuscript for example you can see that power superscripts are really just regular numbers typed at an offset (perhaps rotating the paper around the platen one notch instead of the two that would be a whole line feed). But what about the vectors and the giant sig…
> how did authors handle symbols? Mostly they didn't .. it was handballed to the secretaries of the math and physics typing pool who used stencils, high end typewriters, and other template mechanisms. A good many such secretaries were reasonably talented math and physics graduates themselves who had limited opportunity to be hired to do "a man's work".
A general Fortran code for solutions of problems in space mechanics [pdf]
11–20 of 25 posts
Re: A general Fortran code for solutions of problems in space mechanics [pdf]
#12My first thought was to upload the PDF to Qwen3 and ask it to reimplement in Python using NumPy, Astropy, etc. Have to work on the day job, but could be some educational fun learning and Jupyter plots in my near future. Anyway, the generated code looks promising and contains the requisite green tick and bar graph emojis, so what's not to like?
Re: A general Fortran code for solutions of problems in space mechanics [pdf]
#13It looks like they chose to use the "universal gravitational constant" "k" instead of Newton^s constant, "G": p.23, "k^2 = universal gravitational constant, 1.32452139x10^20, m^3/(sec^2)(sun mass units)" I think "k" was also known as "Gaussian gravitational constant" https://en.wikipedia.org/wiki/Gaussian_gravitational_constan... But the value and unit of "k" given in the Wikipedia page is different. Do you know what…
the value given in the paper assumes the distance in meters I think.
Re: A general Fortran code for solutions of problems in space mechanics [pdf]
#14It looks like they chose to use the "universal gravitational constant" "k" instead of Newton^s constant, "G": p.23, "k^2 = universal gravitational constant, 1.32452139x10^20, m^3/(sec^2)(sun mass units)" I think "k" was also known as "Gaussian gravitational constant" https://en.wikipedia.org/wiki/Gaussian_gravitational_constan... But the value and unit of "k" given in the Wikipedia page is different. Do you know what…
Gauss's constant k is defined as sqrt(G), but for a while the international standard was to define k and then compute G as k^2, which is why NASA refers to it that way.
Re: A general Fortran code for solutions of problems in space mechanics [pdf]
#15My first thought was to upload the PDF to Qwen3 and ask it to reimplement in Python using NumPy, Astropy, etc. Have to work on the day job, but could be some educational fun learning and Jupyter plots in my near future. Anyway, the generated code looks promising and contains the requisite green tick and bar graph emojis, so what's not to like?
The combination of Fortran and AI here starts to be close to 2001. ;)
The X-files AI episodes of the '90's are about as close to 1969 as to today.
All anybody could do then was to use their imagination, but is it all that much different today?
Re: A general Fortran code for solutions of problems in space mechanics [pdf]
#16Idle question: in the days before TeX, when manuscripts like this were hammered out on Remington office typewriters, how did authors handle symbols? In this manuscript for example you can see that power superscripts are really just regular numbers typed at an offset (perhaps rotating the paper around the platen one notch instead of the two that would be a whole line feed). But what about the vectors and the giant sig…
Re: A general Fortran code for solutions of problems in space mechanics [pdf]
#17Earlier quoted context omitted.
> how did authors handle symbols? Mostly they didn't .. it was handballed to the secretaries of the math and physics typing pool who used stencils, high end typewriters, and other template mechanisms. A good many such secretaries were reasonably talented math and physics graduates themselves who had limited opportunity to be hired to do "a man's work".
Non-secretary women were not in short supply at NASA at this time though. The work of Virginia E. Morrell and Bonnie J. McBride a few years earlier, at this same research center springs to mind.
(With the few and obvious exceptions such as Dame Vera Stephanie "Steve" Shirley's ventures)
FWiW I learnt a wee bit from Cheryl Praeger, Cathleen Morawetz, Robyn Owens, et al.
Re: A general Fortran code for solutions of problems in space mechanics [pdf]
#18Idle question: in the days before TeX, when manuscripts like this were hammered out on Remington office typewriters, how did authors handle symbols? In this manuscript for example you can see that power superscripts are really just regular numbers typed at an offset (perhaps rotating the paper around the platen one notch instead of the two that would be a whole line feed). But what about the vectors and the giant sig…
Godement in his analysis exposition briefly talks about this, it was all hand drawn.
When you needed a greek letter you had to stop there, change typeballs, type the greek letter, then put the regular typeball back on.
On the equations the big stuff would be drawn in by hand from stencils.
On a diagram it could be a mechanical (assisted) drawing that was labeled by typing the same font size, like sketch (a).
When you get to sketch (b) though, this one is a reduced photocopy of the original page that was typed on when labeling the mechanical drawing to begin with.
You can see the way that all of the equations and illustrations could very well be place-held in the text draft until a perfect equation or diagram could then be added later by cutting the proper size horizontal strip of paper containing the original drawing, and "pasting" it over the blank spot in the text where the figure goes. Before photocopying to arrive at the priceless original like this where you couldn't always tell where it was cut-and-pasted.
The Fortran printouts from the IBM line printer look like they could be pasted in both at full-size and photoreduced, on one page at page 20.
But a good typist could avoid that for most equations, they could blaze through the text but when an equation came up it took more time to get one equation right than to type many more pages of text.
As can be seen, it was obviously worth it :)
Re: A general Fortran code for solutions of problems in space mechanics [pdf]
#19Source: Working on my PhD in orbital mechanics of asteroids/comets, here are my open source (python/rust) orbital integration tools: https://github.com/dahlend/kete
Re: A general Fortran code for solutions of problems in space mechanics [pdf]
#20My first thought was to upload the PDF to Qwen3 and ask it to reimplement in Python using NumPy, Astropy, etc. Have to work on the day job, but could be some educational fun learning and Jupyter plots in my near future. Anyway, the generated code looks promising and contains the requisite green tick and bar graph emojis, so what's not to like?