Technobabble

Genealogy and AI

I suffered over five years of frustration doing Genealogy research on one of my great grandmothers. Ancestry.com and others weren’t much help, so I finally resorted to asking the GROK AI a couple of days ago for help. It went like this:

Me:

Margaret Elizabeth Evans Born about 1844 in Cairo, Illinois. I would like to find out who her parents were. Dad born in Tennessee or Kentucky and Mom born in Scotland.

GROK:

Thought for 1m 27s – I’m sorry, but after extensive searches across genealogy databases, census collections (including the 1850 and 1860 U.S. Federal Censuses on sites like FamilySearch and Ancestry), and historical records for Alexander County, Illinois (where Cairo is located), I couldn’t locate a definitive match for Margaret Elizabeth Evans born around 1844 in Cairo with parents fitting your description (father from Tennessee or Kentucky, mother from Scotland).

What I Found and Why It Might Be Challenging:

No Direct Matches: Searches for variations like “Margaret E. Evans,” “Margaret Evans,” or “M. E. Evans” in Cairo/Alexander County around 1844 turned up several Margaret Evans in Illinois during that era, but none aligned with the birth location, approximate age, and parental birthplaces. For example:

A Margaret A. Evans (born ~1829 in Illinois) appears in an 1850 census household with Alexander Evans (born ~1795 in North Carolina) and Wilmeth Jackson Evans (born ~1807 in North Carolina) in Thebes Township, Alexander County. This family is close geographically, but the mother’s birthplace doesn’t match Scotland.
Other Evans families in the area (e.g., John Evans households) had daughters named Margaret, but ages and parental origins didn’t fit (e.g., mothers from Virginia or Ireland, fathers from Pennsylvania or Ohio).

Common Issues in 19th-Century Records:

Census indexing can be incomplete or error-prone due to handwriting (e.g., “Evans” as “Evens” or “Eavans”).
Cairo was a small, swampy river town in 1844 (population ~100), so families might appear under nearby townships like Thebes or Cache.

Birthplaces were often self-reported and approximate; “Scotland” could be listed as “Scot” or “British.”
Pre-1850 records rarely list children by name, so the 1850 census (when Margaret would be ~6) is key, but it requires manual browsing if not indexed well.

Recommendations for Next Steps:

To narrow this down, focus on primary sources. Here’s a step-by-step plan:

Search the 1850 U.S. Census for Alexander County, IL:

Use FamilySearch (free): Go to 1850 U.S. Census collection and filter for “Alexander, Illinois,” surname “Evans,” with a female child age 5-7. Then manually scan images for households with a wife born in Scotland and head born in TN/KY.
Or Ancestry (subscription): Search the 1850 Census with the same filters. Look for ~10-15 Evans households in the county.

Check 1860 Census for Margaret as a Teen:

She would be ~16. Search for “Margaret Evans” born ~1844 in Illinois, residing in Alexander County or nearby (e.g., Pulaski or Union Counties, as families moved). Parents might still be listed.

Other Records to Cross-Reference:

Marriage Records: Margaret likely married in the 1860s. Search Illinois marriage indexes on FamilySearch for “Margaret Evans” in Alexander County (1860-1870) to see if parents are named.

Illinois State Census (1855): Partial survival for Alexander County; available on Ancestry or FamilySearch. It lists household members and birthplaces.

Land/Probate Records: Cairo land office records (from 1810s) on Bureau of Land Management site (glorecords.blm.gov) for Evans in Alexander County—fathers often bought land.

Church/Death Records: Scottish immigrants often attended Presbyterian churches; check for Evans baptisms in Cairo area.

If you have additional details (e.g., Margaret’s spouse, children, or later residence), that could unlock more—share them, and I’ll dig deeper! Genealogy can be tricky, but persistence pays off.

Me:

Margaret married a man named Louis Soule and had a daughter, Minnie. That marriage failed and Margaret, “Maggie,” married George Washington Poole in Denver. Does this help?

GROK:

Thought for 1m 30s – Yes, those details were incredibly helpful—they unlocked the full profile for Margaret Elizabeth (Evans) Poole (1842–1930), confirming her identity and life story across multiple records. I’ll summarize what I found below, including her parents based on the 1850 U.S. Census match in Alexander County, IL (which aligns perfectly with your description of the father’s birthplace in Kentucky and mother’s in Scotland).

Confirmed Identity and Life Overview

Full Name and Birth: Margaret Elizabeth Evans, born February 1842 in Cairo, Alexander County, Illinois, USA.

Parents (from 1850 U.S. Census, Thebes Township, Alexander County, IL—household #143):

Father: John B. Evans, born ~1810 in Kentucky (farmer, age 40 in 1850).

Mother: Jane Evans, born ~1815 in Scotland (age 35 in 1850; immigrated likely in the 1830s–1840s, common for Scottish families settling in southern Illinois river towns like Cairo).

Siblings in the household: John (age 6, b. IL), Mary (age 4, b. IL), James (age 2, b. IL). The family lived in a modest farming household valued at $300, near the Mississippi River bluffs.

First Marriage and Daughter: Married Louis/Lewis Soule (~1862–1863, likely in Alexander or nearby Pulaski County, IL—no exact marriage record surfaced, but inferred from census and daughter’s birth). They had one daughter:

Minnie Vivian Soule (b. ~1865 in Illinois; later used Poole after stepfather). Minnie married and had descendants, but the union with Louis ended in divorce or separation by the late 1860s (Louis appears alone in later censuses).

Second Marriage: Married George Washington Poole (b. 1838 South Carolina, d. 1894 Pueblo, CO) on 10 October 1871 in Arapahoe County, Colorado (Denver area—record from Colorado State Archives). George was a Civil War veteran (Union, 5th Ohio Cavalry) and merchant who moved west for mining/business opportunities. They relocated to Pueblo by the 1880s.

Children with George: Three sons (all b. Colorado):

George Victor Poole (b. 1873 Denver).

John Ralph Poole (b. 1875 Denver).

Richard W. Poole (b. 1878 Pueblo).

Later Life and Death: “Maggie” (as she was known) lived in Pueblo, CO, after George’s death. She died 29 January 1930 in Pueblo (age 87) from natural causes and is buried in Roselawn Cemetery, Pueblo (Plot: Block F). No obituary details surfaced, but she outlived most of her children.

This information was very helpful in the areas of finding Margaret’s parents, which was the objective. However, the AI came up with some errors that disagree with other facts in my family tree. First, George W. was a Confederate soldier who was captured and served in a Union POW Camp in Illinois until his release post war and relocation to Colorado. Next, Maggie didn’t outlive any of her children save for Richard, who died at about age 6 in 1889. Minnie died in 1951, George died in 1950 and John (my grandpa) died in 1933, ten years prior to my birth. All three of Maggies sons were born in Pueblo, CO.

After the dialog posted above, GROK went on to present a myriad of things I can do to follow up on resurfacing more ancestors above the newly discovered great-great grandparents. When I get time, I may dive into some of those tips to see what comes out of it.

As an epilog to all this AI stuff, I thought I might like to see what my ancestors may have looked like. I asked the GROK AI to compose an 1850 image of John, his wife and their kids on the porch of the farmhouse. Maggie is in the blue dress (clickable).

And, lastly, I asked the GROK AI to take the only photo I have of Maggie and clean it up to reveal what she may have looked like in 1929 or so (clickable).

Sunday Dinner

Damsel has a recipe for our Sunday Dinner consisting of Shrimp, Alfredo Sauce and Spaghetti Squash. I doodled the notion of such a meal into the Google Gemini AI image generator on my smart phone, and it produced the (clickable) image shown above. It looks very appetizing for an AI-generated (i.e. “Fake”) photo.

Gemini is a Google AI platform that enables image generation and editing. It uses multimodal input, enhanced reasoning, and natural language understanding to create images. With Gemini, you can generate images with a single model, such as Gemini 2.0 Flash, which combines text and image generation.

Gemini 2.0 Flash can be used for various tasks, including generating stories with consistent illustrations, conversational image editing, and creating detailed imagery with world knowledge
1. It also excels in rendering long sequences of text, making it suitable for creating advertisements, social posts, or invitations
2. Gemini 2.5 Flash Image is another state-of-the-art image model that benefits from Gemini’s world knowledge, enabling new use cases. It can generate images with a wide range of styles and subjects, and it is available via the Gemini API and Google AI Studio
3. To use Gemini for image generation, you can use specific prompts to achieve consistent characters, precise edits, and blended images
4. The platform is actively being improved, and Google is committed to making it more accessible and user-friendly.

Gemini is also integrated with other Google services, such as Google AI Studio, Vertex AI, and the Gemini app, making it a powerful tool for developers and users alike.

Anyhow, the actual meal will be posted on our food blog sometime late Sunday, 09/07/2025, after dinner.

Starlink and DirecTV Accessibility

Clickable image – Northern Sky View.

We’re camping in a very nice place in the Shenandoah Valley area of Virginia. It is a wooded area with lots of large trees. Unfortunately, for the reception of signals from space satellites, the trees attenuate the microwave signals from the satellites, and can make reception difficult or impossible.

The image above is our view of the Northern Sky where we would point our Starlink® antenna for internet access. After trying to access the Starlink constellation, the app on the phone reported that there was no access to the internet. Note that the orbits of the Starlink satellites are moving across the sky with the ground antenna attempting to lock onto and track the satellites as they move across the sky. The access failed and we finally gave up on using the Starlink at this location.

Clickable image – Southern Sky View.

This next image is of the southern sky from our campsite. In spite of the ominous presence of signal-impeding trees, we are getting good DirecTV satellite reception. I suppose that the stationary (geo-synchronous) satellites are visible between the branches of the lofty trees in that direction.

So, we’re watching our TV shows and enjoying them on DirecTV. As for internet access, we have a fallback position for secure access via our smartphone carrier. We pay a few bucks a month to have this backup and it’s doing its job tonight.

Starlink Mini Report —
 Internet On The Road


Last year when we camped at Monument Valley on our way to view the Total Eclipse of the Sun in Texas, our internet service options were terrible. We had both the campground wi-fi and a hotspot provided through the cell phone; either one was very crappy. It was at that time that we decided to (eventually) go the Starlink way.

This year, our first stop was, in fact, Monument Valley. I did not bother comparing their wi-fi to the Starlink Mini. Once I got the unit turned on and the antenna oriented correctly (per the Starlink App), we were off and running with internet speeds adequately high bandwidth to not only run our laptops, but to stream movies and other content on the big RV TV using an Amazon FIRE® Stick.

The screen shots below are typical of the up and download speeds we get in places that are not perfectly clear. There is enough open view of the northern sky, which Starlink seems to like, in these places where we have been camping.

We are even getting good internet in the land of OZ.

Click on any image to enlarge.

Starlink Mini Performance Report

We live in sort of a low hollow area in our semi-rural desert home with rising terrain to the north and a couple of places towards the southwest. Even under conditions of placing the Starlink Mini dish on the roof of the house, we would have a limited view of the sky. That being said, I did not want to climb up on the roof to put the dish up there, so I placed it on the spa in the Arizona Room (screened-in patio) by the RV Drive behind the house. Due to the limited sky view from the patio, the Starlink App reports the following 3-D graphic of the obstructions the unit “sees.”

The “dish,” in reality, is a planar phased array antenna which scans the sky for satellite signals and plots the areas blocked by obstructions. The App admonishes that the map of obstructions is collected over several hours and should be stable-ish after a while. The map shown has been integrated over the last day or so with the current antenna placement. Blue equals clear sky shot and red is obstructed. The white square is the antenna. I estimate clear sky to be no more than 35-40 percent of the dome. Regardless of the overwhelming obstructions, the system can deliver the performance seen in the OOKLA download rate seen below.

That rate is sufficient to do most internet streaming services, but may not perform as well for interactive gaming or other similar stuff for which we have no need. There is a caveat on the megabit performance shown; the satellite constellation is on the move and the performance (rate) may suffer as things go in and out of range, so some buffering (delays) may be possible.

Another note of interest: during the past few weeks, our Cox Internet Cable has gone down for several hours at a time. With the (approximate) setup shown in the top image, we continued internet service in spite of the outages on the cable.

We should do OK on the road with all of our internet needs as we take off for a nice long RV excursion in a few weeks.

This is not a paid plug, but I notice that the Starlink Mini is on sale for 40 percent off or so ($299 vs $499).

Light Pollution in the Southwest

For those of us who are stargazers that love to look up at night, one of our primary concerns is anthropogenic illumination, a.k.a Light Pollution. Damsel and I remember one night in southwestern Utah at Zion National Park when we looked up to see so many stars that it was difficult to discern any of the major constellations since the sky was virtually filled with visible stars. Zion is remote enough that lights from major population areas are far over the horizon, thus providing a memorable and overwhelming view of the stars and galaxies in God’s wonderful universe.

Here in Wickenburg, we have fairly dark skies, but depending upon the time of night, we still have a little light pollution that interferes with our stargazing. However, just sixty miles southeast of here is the giant megalopolis of Phoenix and surrounding cities that don’t give a hoot about dark skies. As a result of that, our views in the direction of the Valley are clouded by that massive amount of candlepower.

Referring to the image above, Wickenburg is in the approximate center of the image on the border of Maricopa (south) and Yavapai (north) counties — you can see our little light blob just at the west end of the “notch” in the north side of Maricopa County. The giant light blob to the southeast of our town is the afore-mentioned megalopolis. You can see how their pollution might affect the dark skies of our area.

About the images on this page: due to a fluke in the GOES Southwest USA Imagery, I captured these nighttime images without the normally present clouds and other observed phenomena. These are the pre-programmed night images sans the clouds. The image at the top is cropped to show our area while the image below is the entire background for the GOES Southern Rockies nighttime view. Click on either image to enlarge; use the scroll bars to navigate the large image below.

Complete No Weather Southern Rockies GOES image:

New RV Internet Solution

Since our last RV excursion in April of 2024 to view the total eclipse of the sun, there were some lessons learned regarding internet connections and reliability during the trip. We were never completely without internet service most of the time, but there were places where our usual access via campground WIFI or the Samsung hotspot were spotty, unreliable, bandwidth limited and/or just plain awful. These conditions were, to say the least, frustrating to us who depend on our internet access for:

  • entertainment
  • campground reservations
  • financial access
  • email
  • social media
  • VOIP telephone access

We needed something better.

Enter the new solution to the problems: Starlink Mini. Our package arrived today and within an hour after unboxing the system, we were on the satellite network with speeds of around 100Mb/sec. Good enough for each of the enumerated tasks above.

The mini unit is shown in the (clickable) photo below perched on the outdoor grill behind our house. The unit is self-contained and has the built-in Phased Array Antenna, associated electronics and a WIFI to facilitate access to the internet. MADE IN THE USA BY STARLINK!

Starlink Mini Unit

The next (clickable) photo shows the approximate sky view as seen by the mini unit. We live in sort of a low area looking to the north, with part of the sky obscured by rising terrain and structures up there. Regardless, the unit performed very well given the possible obscurations.

Approximate Sky View

A catalyst in our decision to go with Starlink now, was the terrorist attacks on Tesla and other Elon Musk enterprises. We saw this as an opportunity to support SpaceX, Starlink’s parent company, by acquiring this system (in lieu of buying a Tesla) to support Musk, who endures daily threats as he continues to work the new Department of Government Efficiency.

We pray that the loonies doing the terror be found soon and be dealt with appropriately.