Monday, October 21, 2019

Publishing and Buttons

Switching to self-publishing has had an unexpected and beneficial effect on my attitude about writing.

When I started out, long before self-publishing was an option, I was writing for the sheer pleasure of it, for the happiness it gave me, for the delight in the act itself. I wrote what I liked, and I liked what I wrote.

That changed as soon as I became traditionally published. I started focusing on writing what a commercial publishing house would accept. I became almost obsessed with pushing all the right buttons. It hampered my creativity and it certainly limited the fun. Much of the time, writing wasn't fun at all.

After I switched to self-publishing in 2009, that near-obsession stayed with me for a while, but it started to fade, and then it evaporated entirely. In time, I stopped worrying about those buttons and reverted to writing to please myself again. It's been wonderful, liberating. This attitude isn't likely to result in bestsellers, but it does result in a happy writer.

And so, after all these decades and 29 books out there, I have come full circle. Once again, writing means to me being a man alone in a room happily pushing his own button.

So to speak.

Sunday, September 22, 2019

The Day I Was a Whacked-Out Hippie on a Bus in California

Being a random memory from the Space Age.

From 1971 to 1974, I worked on the Viking Mars lander program at Martin Marietta in Denver. I was part of a small team (three men most of the time, with two to three other people added for brief periods) developing the software that would be used to determine the timing and duration of the Viking lander’s deorbit burn when it was in orbit around Mars.

The orbit would be known(ish), Mars gravity would be known(ish), the atmosphere would be somewhat known(not-very-ish), and the desired landing site would have been specified. Make some assumptions, turn on the deorbit rockets, and head down to Mars! With the assistance of a few gazillion lines of code.

Which we developed in FORTRAN on a CDC 6600. The original plan was for the software to be run on that machine during the actual mission. However, Jet Propulsion Lab, JPL, in Pasadena, California, exerted its considerable political weight and it was decided that during the mission, the software would instead be run on a Univac 1108 at JPL.

We shipped our software to Pasadena and told them to load it onto the 1108 and have at it. However, what had worked just fine on the 6600 failed miserably when transferred to the 1108.

We tracked down the problem and made the changes.

Or so we thought. JPL said it still didn’t work. (As was always their way, they made it clear that all would have been just hunky dory [or copacetic, as people in the Apollo program used to say] if the software had been written at JPL in the first place.) (Yeah, right.)

Time was getting short. Time is always getting short in the aerospace biz. A few of us were sent out to JPL to track down the bugs and run simulations and verify that all was well. Quickly.

I was out there, on the very edge of civilization, for three weeks, getting too little sleep, spending my days and much of my nights at JPL, reading printouts, writing my changes on the printout, changing punch cards, submitting card decks, waiting for new stacks of printouts, repeat. By the end of the three weeks, desperate to get it done and go home, I spent a few days without sleep, working around the clock.

Finally done with my part, I went back to the hotel like a zombie, packed, checked out, and took a bus to the airport.

This was in 1974 (or just possibly late 1973). I had long, red hair, worn in a ponytail, and a full, rather bushy red beard. I was wearing a t-shirt, jeans, and sneakers. My eyes were gruesomely bloodshot and had huge bags under them. I sat in the bus swaying from side to side, falling forward, drifting into sleep, then snapping awake again.

I don’t even remember what the bus was. Some short of shuttle between hotels and the airport, I suppose. I don’t even remember getting on it. I do remember that it kept stopping to pick up tourists at hotels and once, oddly, at the Hearst Castle.

Most of the tourists seemed to be older English couples dressed formally informally. They kept turning to stare at me and then turning away again quickly when I met their eyes. Very British. I imagined them whispering to each other that they had heard that the drug problem was bad in California, and here was living proof. Just look at that poor young man, his mind destroyed by drugs. Shocking.

The rest of the story is anticlimactic. I got to the airport, got home, went back to work, got laid off once all the work was done and the company had been paid by NASA—a typical aerospace story.

But I’ve sometimes imagined myself trying to reassure those tourists that I wasn’t on drugs. My words slurred, mumbling incoherently, swaying, my red eyes open wide in earnestness, waving my hands about, I would have tried to tell them that I was working on sending stuff to Mars. And before that, you know, moon, men, men on the moon. Mars, people. Moon.

For years afterwards, they would have bored their grandchildren with tales of their trip to California and the wild-eyed, hairy hippie they saw there, his mind destroyed by drugs, ranting about Mars and the Man in the Moon. “Tragic. Probably long dead in the gutter, the poor young man. Let that be a lesson to you, children.”

Writing this reminds me of the time, years earlier, when I was in graduate school and drove down from Indiana to Mobile to visit Leonore and her family, my first time in the South, through the heat in my un-airconditioned Volkswagen. Then, too, I had a beard and wore my hair in a ponytail (ya know, grad student). I was dressed in shorts and sandals. I was so na├»ve. I had no idea why the locals were glaring at me. I smiled at everyone. It must have been a year or two after Goodman, Schwerner, and Chaney were murdered. In the parking lot of a grocery store in Mobile, a well-dressed white woman glared at me through the windshield of her expensive car and tried very hard to run me down. But that’s another story.


See below for some of the nasty details. They’re not indispensable to the story, but they might be of interest to some. Keep in mind that all of this work was done using punch cards.

Yes, FORTRAN is always all caps. At least, in this household. It was THE language for scientific computing! With GOTOs, as God intended! (Not that there was a real alternative, although I did later run into mercifully short scientific programs written in COBOL, gasp.)

The CDC 6600 was a great machine for scientific computing by the standards of the time. One of its best features was its 60-bit-word architecture, meaning that we could do the job without bothering to double-precision any variables.

At a later job, I programmed on a Univac 1108 extensively and liked it, but it used a 36-bit word. The difference was important for this story. The calculations done by our software were long enough and iterative enough that too much precision was lost on the 1108 compared to the 6600. That was why the code gave erroneous results after it was transferred from Denver to JPL. After a few iterations, the values of a lot of the variables in the program were, in effect, random numbers. To fix that, we had to go through the code and convert everything to double precision. Gazillions of lines of code meant zillions of variables that had to be changed in many, many places. Inevitably, we kept missing some of them and having to go searching through the code again..

In addition, we had used a nifty but dangerous FORTRAN thing called Block Common, also called Unlabeled Common, which was a way of transferring variable values between subroutines and functions without putting them in argument lists. It meant that many more places where variables had to be declared double precision and more opportunities for overlooking them. We finally decided that we had to break our enormous block common into numerous (jillions) of separate labeled common blocks. It was ghastly.

Tuesday, July 16, 2019

Just published: My memoir of working on the Apollo project

Just in time for the 50th anniversary of the Apollo 11 landing, I've published my short memoir of my time at NASA working on the Apollo project:

Thursday, October 18, 2018

KDP Print Cover Templates–Beware of This Glitch

We recently finished a client’s book that’s 91 pages long. I downloaded the KDP cover template. Because those come in ten-page increments, I was given the template for a 100-page book. The template includes space for text on the spine, so as usual I put the book’s title and author’s name there.

When I submitted the book for publication, it was rejected because a book has to have at least 100 pages in order for the cover to have text on the spine. Fair enough, but KDP apparently doesn’t have an appropriate template for a book of 91-99 pages in length. Instead, you get the 100-page template with space for text on the spine, which causes an error.

So be aware of this problem. If your book is under 100 pages but the template shows a space for text on the spine, don’t put anything there.

Saturday, September 29, 2018

Wednesday, September 26, 2018

Did your CreateSpace book(s) get moved to someone else’s KDP account?

Of course that shouldn’t happen, but I just encountered a case where it did. If there’s one such case, there surely are others.

A while ago, I went through the process of transferring the print editions of all of my books and my wife’s books from our CreateSpace accounts to our KDP accounts. This was before Amazon started doing anything automatically. The process went smoothly. For a few hours, the books were no longer listed on CreateSpace but hadn’t yet shown up on KDP. That was disturbing, but eventually, the books did show up where they belonged.

As part of our self-publishing services, we upload our clients’ books to both CreateSpace and KDP. I have moved some of our clients’ books from CS to KDP, also without any problems. I’ve been checking other client accounts to see if Amazon has done the move itself.

Yesterday, I checked the CS account of Client A, who had one self-published book listed there. The book was no longer listed on CS. Because of a password problem, I couldn’t check Client A’s KDP account to look for the book there, but I assumed all was well. Later, I checked the CS and KDP accounts for Client B, who also had one self-published book on both. The print edition of that book was no longer on CS, but it is now on KDP, as it should be. Amazon moved it correctly. However, Client A’s print edition, which had disappeared from CS, is also on Client B’s KDP account! Amazon moved the print edition of Client A’s book to Client B’s KDP account.

Client A will contact KDP in hopes of sorting this out.

Not only is this awful, it’s also a remarkable coincidence. Given how many self-published authors use both CS and KDP, the chances of some kind of software/database error accidentally moving one of our client’s books to another client’s account must be minuscule. Is it possible that Amazon’s software has stored cookie information from two different logons from my computer? It seems extremely unlikely, but if so, this is alarming for people who use any Amazon sites on shared computers.

I’ve been wondering how Amazon knows which KDP account to move a CS book to. It can’t be using login information. You could be using the same e-mail address to log into both CS and KDP, but not necessarily. Both sites should have your Social Security Number or other tax ID, so those could be compared. Either comparison should have avoided the error I described above. So how did this happen? And how can anyone be sure it’s not happening to many different writers?

Check all of your books on KDP carefully once the dust has settled from this move. That’s not very useful advice, but it’s all I can think of.

Saturday, March 03, 2018

The Aliens beneath Our Feet

SETI looks outward. The Search for Extraterrestrial Intelligence looks for signals from alien civilizations elsewhere in the universe. The odds are long and the cost is high, but the rewards for success will be great. That search must continue. However, I think we would profit from redirecting a small portion of SETI’s money and resources to a much closer and more accessible target: earthly dust. We should be looking down as well as up.

In my short non−fiction book Dust Net, I predicted the advent of nanoscale communication and information−gathering devices the size of dust motes, extremely powerful, and scattered across the earth. These will be developed in the fairly near future for a number of purposes, benign and not so benign. I also speculated that extremely advanced versions of such devices might already be present, deposited on Earth by alien races.

In this post, I want to expand upon the idea of those alien devices.

Let’s assume the existence of a great number of technologically advanced races within a few hundred light years of Earth. That’s a very reasonable assumption. Let’s further assume that faster−than−light travel isn’t possible; that’s very probably the case. I think that developing a technologically advanced civilization requires curiosity about the universe and how it works. That implies curiosity about the possibility of intelligent life existing elsewhere, so I think it’s reasonable to assume that those advanced races are as curious about life on other worlds as we are.

Those advanced races want to visit other worlds, but distance makes that unfeasible. However, they have the technological ability to send out unmanned interstellar vessels at a reasonable cost—or at least a cost they’re willing to pay. What form would those vessels take?

They could be large spacecraft filled with data−gathering sensors, recording devices, artificial intelligence computers, and communications equipment. Since no UFO sightings have been validated, we can assume that if there are such ships, they must not be both large and close, or we would have seen them.

Perhaps the ships have some sort of cloaking technology, or surfaces made of advanced metamaterials, so that we can’t see them. However, we watch the skies in numerous and increasing ways, and we watch the earth from above in numerous ways. Before long, we’ll be watching the earth constantly from the moon, with increasingly powerful instruments. Before much longer, we’ll be looking in all directions from the surface of Mars. No matter how advanced the camouflage of alien ships, the chance of them being detected is already high and will keep getting higher. If they exist, they have successfully avoided detection so far, so they can’t be spending more than very brief periods of time anywhere close to the earth. Even at our current stage of detection, they would have to be operating no closer to us than Mars—or at a distance of about 50 million miles (the closest that Mars approaches Earth).

That wouldn’t be a problem for them, in some respects. Being able to send complex unmanned probes over interstellar distances requires very highly advanced technology, perhaps advanced enough that it can collect all the data the aliens want even from 50 million miles away. Of course, this would prevent them from collecting physical samples, such as air, water, and bacteria. Even if that were acceptable to them, the data they collected would be fairly coarse. They would not be able to examine our world at a fine and detailed level. The restricted nature of their observations would be frustrating to human scientists and would surely be just as frustrating to alien ones. It would probably be unacceptable, given that they have a much better alternative.

That alternative is what I called Dust Net.

Human beings will create Dust Net in the near future. It will first take the form of simple, microscopic servers scattered around the world to create a communications network accessible to everyone and secure from interference by governments or malicious private interests. With time, these servers will increase in power and will be reduced to nanoscopic size. No bigger than specks of dust, these particles, these motes, will drift with the wind and float on the surface of oceans and lakes, becoming ubiquitous. Their social and political impact will be enormous even before they evolve, as they inevitably will, into instruments of surveillance and data gathering. There will be multiple separate nets, products of governments, corporations, and private groups both good and evil. Mingled among them will be the alien nets.

As I explained in the book, networks of such motes will be able to record immense quantities of data. The advantages for alien observers are obvious. Their motes will be safe from observation or interference. Even without propulsion systems, they will eventually spread everywhere on the surface of Earth. They will gather all the information a curious alien civilization could want.

We are already developing ways for swarms of autonomous drones to cooperate. The much more advanced alien motes are surely capable of cooperating in large enough numbers to, say, dissect an animal corpse for detailed analysis. With sufficient data storage capacity and sufficiently advanced recording devices, they can store a complete digital record of plants and animals, obviating the need for physical samples.

In order for such swarm cooperation to exist, the individual motes have to communicate with each other. Perhaps they use some method of communication that we haven’t discovered, meaning that we won’t be able to detect them by eavesdropping on their communications. It’s also possible that they coordinate their actions only by watching each other, avoiding the need to pass signals. However, if they do communicate, and if they use radio or light signals, that’s something we can try to detect. In addition, the swarming behavior itself would make the motes stand out from natural dust.
The advantages of exploration of alien planets by means of such dust motes applies to all advanced alien societies, so if there are such motes on Earth from one alien civilization, there are surely similar networks of motes from other alien societies also present on Earth.

In Dust Net, I speculated that some of the motes created by humans will be designed to destroy other motes. Corporations will do this as a form of industrial espionage. Governments trying to control what information their citizens have access to will try to destroy the motes that provide the access of which the governments disapprove. Eavesdropping motes will expose government secrets, so government motes will try to destroy those. Governments will try to limit observation of their territory by enemy motes, so they’ll produce motes capable of identifying and destroying motes from other countries.

All of this exposes the aliens’ motes to danger. The aliens must assume that hostile mote networks already exist on the planets they send their motes to investigate. Perhaps the alien motes have the ability to protect themselves, but it would be better if they evaded detection entirely. Therefore, they probably look like inanimate, naturally occurring local dust motes. We could microscopically examine untold numbers of specks of dust and never pick out the alien motes hiding among them.

How do motes from different alien cultures interact? Do they interact at all? I think it’s fair to assume that in general, alien civilizations don’t need or want to interfere with motes from other alien civilizations. If they can identify each other, they probably leave each other alone. Perhaps some of those civilizations are sufficiently pacific and socially advanced that their motes exchange information with each other. That increases the amount of observational data gathered without extra cost.

On the other hand, there’s a good chance that some alien civilizations are located close enough to each other to interact directly, with trade or war. If it’s trade, then their mote networks on other worlds, such as ours, are probably designed in advance to cooperate with each other. But if two civilizations are at war, then their mote networks probably are, too. Their motes are here and on other worlds, not for the purpose of gathering interesting data, but in hopes of finding something—science, engineering, weapons—that will give them the edge in the war back home. Their mission therefore includes keeping the other civilization’s motes from finding that dangerous information first, so they are designed to identify and destroy each other. As a precautionary tactic, their motes might well be designed to destroy other alien motes, even ones from peaceful civilizations too distant to be a threat. I think that would be our approach if we were those aliens, and it seems reasonable to assume that warring aliens are just as unpleasant as we are when we’re at war.

This suggests a way we could detect the alien motes: by looking for the aftermath of battles in the nanoscopic realm.

It’s not practical for aggressive alien motes to blast the enemy with destructive rays or cannon shells, so we wouldn’t be looking for explosions or tiny bursts of radiation. Such a war is more likely to be conducted at close quarters. Attacking motes act much like predatory insects—injecting the enemy mote with destructive acids or simply tearing it to pieces.

The dead motes should be the object of our search. Those injected with destructive fluids probably still look outwardly just like ordinary dust motes and so are not detectable. Remnants of motes that have been broken apart are a different matter. The attacking motes could take the time to disguise remnants of the enemy to look like just native dust motes, but that’s surely impractical just because of numbers. Therefore, if we looked at vast numbers of dust motes, we might be lucky enough to find some of those tiny chunks of disabled technology.

How do the alien motes get to earth? And how do they send their data back home?

One possible answer to both questions is that an alien civilization could produce vast numbers of such motes—say by cannibalizing entire planets to provide the materials—and sending streams of them out in all directions. Interstellar space could be filled with the devices, providing a chain of relay stations to send data back to the home planet. This is obviously excessive.

A far better approach is for the aliens to send out large interstellar ships packed to the brim with fabricators: microscopic factories whose function is to churn out nanoscopic motes. The big ships release fabricators as they pass by stars that have planets. The fabricators drift down to the surfaces of the planets and begin creating motes using materials found onsite. Such fabricators are obvious targets for our own search. They are larger than the motes—microscopic, rather than nanoscopic. And it’s hard to disguise them as anything but what they are, because they are emitting streams of newly fabricated motes.

How is the data returned to the aliens’ home planet? It seems highly unlikely that an individual mote can send a signal powerful enough to reach another star system. But a huge number of them working in concert can do so. We could detect that.

Perhaps a ship passes by to pick up the signal. That way the signal can be much weaker, possibly below our ability to detect it. However, the passing ship would be detectable. As I argued at the beginning, we can dismiss that idea based on the lack of verified sightings of such ships.

Perhaps small groups of motes, loaded with data and operating as one, can escape Earth’s gravity and be picked up by a passing ship at a great enough distance that we can’t detect it. We probably wouldn’t detect a small clump of motes leaving Earth, either.

Detecting motes through the method they use for returning data to the home planet doesn’t seem promising. The other ways I listed above offer a much better chance of detecting the alien motes.
Should we start the search now? It’s feasible with existing technology. It will be even more feasible when Dust Net exists. That’s probably 20 years away at most, and possibly closer to 10 years. Then we can design motes whose sole job is to examine the dust around them and look for alien motes. Obviously the number of dust specks that could be scanned by using Dust Net, and the number of locations on Earth where the scanning would be done, would far exceed what we can achieve today.
Nonetheless, I don’t think we should wait even another 10 or 20 years. The odds against finding alien motes are high with current technology, but the cost would be a fraction of the current outer−directed SETI, and the rewards for actually finding alien motes would be immense.

Unlike SETI, the discoverers won’t have to depend on information given to us by aliens, whether intentionally or as a byproduct of their detected broadcasts. With SETI, the information could be significant, or it could be fairly trivial. By contrast, alien motes will be highly advanced alien technology actually in our hands. Given the way the world now works, that alien technology will be the possession, not of the human race, but of the nation that discovered it. The nation that possesses it will leap ahead of the rest of the world in power and dominance even more than the Industrial Revolution vaulted Britain ahead of the pack centuries ago.

This could all be fantasy. The alien motes might not exist. But we can’t ignore the possibility that they do. Even now, searching for them would be relatively cheap compared to the cost of SETI and trivial compared to the military budget. The search should begin immediately.