Friday, September 18, 2020

LTV Steel in East Chicago (ArcelorMittal Blast Furnace #4)


The predecessor LTV plant in Chicagoland was in Chicago. This plant was an expansion of their Chicagoland operation. I was able to determine that LTV was the west part of the Indiana Harbor complex from this statement: "2002 Ohio-based International Steel Group (ISG) purchased the assets of Acme Steel and LTV Steel Company including Cleveland, Hennepin and Indiana Harbor West" [ArcelorMittal]

Aug 3, 2020: ArcelorMittal is laying off nearly 900 workers because the Covid-19 recovery is weak. This would include the west part (former Inland Steel) as well. [AgMetalMiner]

Aaron Metzger posted
4 furnace Indiana harbor
badge icon
Bleeder pop
You should be around Inland #7 when it goes off ,, nothing compares .
I remember them days seeing the bleeds open.

Aaron's photo allowed me to confirm that #4 is the furnace on the right. He took a shot of the northeast side of the furnace.
Dennis DeBruler commented on Aaron's post
Judging by the roofline of the building, the ore bridge on the left and the pipes going to the right, you have taken a photo of the furnace on the northeast side. So I presume the number for the furnace on the southwest side is #3.

badge icon

 yes it is

Dennis DeBruler commented on his comment

 Thanks to your two photos, I think I have finally figured out the standing blast furnaces in Indiana Harbor.

Ted Lee posted
#3 and #4 at A.M. west East Chicago.
Did refractory on 4 BF for years, shotcreting and form and pour the runners.
3 is down for good.

Thursday, September 17, 2020

Facebook Lemonade: They no longer abbreviate URL displays

Facebook's Doomsday has happened. But I have discovered an escape to the classic version so that I can still get examples of how they did stuff better.

Some URLs can be rather long. When a long URL is shoved into Facebook's skinny timeline display, it consumes a lot of screen lines.

The classic version did a good job of abbreviating them so that only one screen line was consumed. Specifically, it included the domain name and the end. Actually, now that I look at it, it is smarter than using just the end. Now I'm curious what their algorithm was. But I won't be able to study how they abbreviated URLs until, hopefully, they copy that code forward into the new version.

Some URLs can fill a screen with quite a bit of gobbly-gook.

Facebook fixed this in less than a day! Kudos for Facebook.

Wednesday, September 16, 2020

A Horse-Powered Ear Corn Grinder

Dale Buxton posted
I found this at a barn sale in Nebraska and couldn't walk away..... it's about 400lbs.
Problem Is I have no idea what it is. Please help out.

Dale added this in response to question about what the other side looked like.
It looks like one made for ear corn. The cutter with 3 hooked blades would cut the entire ear into smaller pieces and the center piece looks much like some other grinders I have as a breaker to make yet smaller pieces and the ones I have then had a set of burrs to grind it down even finer. The ones I have operated horizontally but this one looks to have ran in the position it is sitting in. May have had a sheet metal hopper at that upper shoulder.
[Other comments indicate it would have had a funnel shaped hopper on top. And the wheel could adjust the size of the resulting grind.]


When I was writing about the Cos Cob Power Plant, I wanted to reference my notes on ComEd's Fisk Power Plant using the link But when I tested that link, it didn't work! So I looked at the HTML of the target notes. What I expected to find was the named anchor:
<a href="" name="fisk"></a>
What I found was:
<a href=""></a> 
Note that the "name" attribute is missing! The href attribute is something that Blogger adds after I type in <a name="fisk"></a> and it's extraneous. BTW, I learned years ago that <a name="fisk"/> doesn't work.

The Midwest notes had three named anchors, and all three of them were missing the "name" attribute. So I added it back in. The new version no longer adds a bogus href attribute, which is good.
<a name="fisk"></a>
I quickly spot checked another post that had named anchors, and it was OK. So I lost some sleep trying to figure out how to find the destroyed named anchors in my thousands of posts. The new version supports a "body" search which looks at the HTML as well as the visible text. So the query I needed was the boolean expression: and not body:name=
But Blogger doesn't support boolean expressions. (But believe me, the new search is far better than the search in the legacy version since the author's search in the legacy version broke April 3, 2018. I've been having to find posts using just a label. In fact, the search function is the only thing I have found so far that is better in the new version.) So I needed to do two body queries and eliminate from the first result those posts that appear in the second result. But the results of these searches is so big that I haven't taken the time to even force a loading of all of the results.

Then yesterday I was working on my Met "bridge to nowhere" notes and discovered that the forward reference did now work. So I switched to HTML and searched for "/null" to add " name="met"". But I did not find it! So I added "zzz" to the notes where the name should be and looked for zzz in the HTML. To my horror, there is no <a> element for a named anchor! So I can't even search for "/null" to find where I have problems.
<a href="">Dennis DeBruler</a> The former "L" bridge in the background. Now it is just a signal bridge. This "L" route was replaced by the Dearborn subway.</td></tr>
zzz<br />
The Metropolitan West Side Elevated Railroad was the third one built in Chicago and the first to use electric traction. [<a href="" target="_blank">GarfieldPark</a>]
 So I added "<a name="met"/> to see if it still needs the </a> text. The resulting HTML is:
<a name="met">
That is not correct HTML, but it did work when I tested it.

So now I have the situation that Google has destroyed some of my named anchors and I have no way of finding what needs to be fixed. Named anchors is a feature that I use rather frequently so I was glad when I saw that the new version supported adding them. Google has since removed that support.

Unlike Google destroying URLs, I have no idea what causes it to destroy named anchors so I don't know what to avoid doing. In fact, I don't even know if it was the new or the legacy version that destroyed them! They may have been broken for years, and I just now happened to need a broken one. 

In the case of URLs, I have to avoid removing the formatting of text. I did a quick test. This bug is still there even though I found and reported that content destruction bug soon after they released the new version. (The correct domain in the screenshot is not At least they improved their URL display a few weeks ago so that it is easier to check the URL content.

I did force the entire results of the "body:name=" results to be loaded and I saved the results below as a series of window captures so that a year or so from now I can see how many more named anchors Google has destroyed. But before I did that, I took a nap. After sleeping on it, I realized that would give me a list of posts that would have damage, but I wouldn't know the names that got lost. But then it occurred to me that I could find the lost names by searching the blog for links to the name. To test this theory, I searched for posts that referenced the Midwest posts:
And got:
If this doesn't remind me of the names, then I can go into a post, switch to HTML and search for ".html#" to find the names. Hopefully, when I learn the names, I can remember where they belong in a post.

Current posts that have named anchors

If sweeping out 21 screenshots and saving them wasn't a torturous enough waste of my time, I remembered that I have a second blog. Fortunately, I don't cross reference as much in that blog.

Tuesday, September 15, 2020

Aban/D&SL: piers in the Kankakee River


Ken Morrison posted
A real ghost-there were never even tracks here. The Decatur & State Line was never built-apparently the records and plans burned up in the Chicago Fire. But it was started...the better-known evidence of that are the bridge piers across the Kankakee River just south of here. This is at Warner Bridge Rd. and IL 102. The angled row of trees lines a small length of ROW, looking SW
"The line was chartered in 1869, when construction over the river began, but the project quickly lost it's financial backing partly because of the Great Chicago Fire. Had it been constructed, the route would've run through Bellflower, Farmer City, Saybrook, Chatsworth, Wilton Center, and Frankfort, among other towns, before connecting with the Chicago Rock Island & Pacific."
The D&SL was at least partially graded and bridge work partially completed too but went broke before any rails were laid. The Wabash (WStL&P) then owned financier Jay Gould looked at this property and it’s charter to build into Chicago. The Wabash instead bought the bankrupt and partially built Chicago & Strawn RR instead and built north from Strawn (Risk) IL to Chicago. I believe part of IC’s Bloomer Line is built on part of the D&SL’s grade.
That is interesting. It would be neat to see a map of Illinois ghost railroads.
Roger Kujawa
 before my last computer crashed, I had put pushpins on Google Earth wherever there was evidence of the D&SL. Amazingly, they all lined up. Included a stretch of the Bloomer Line through Cropsey.

Dennis DeBruler commented on Ken's post
I wondered about the history of these piers, June 3, 2016.

This street view is looking the opposite way through the line of trees that Ken took.
Street View

Facebook Lemonade: the post link for a share from the reading list is not provided

This share was accessed from my reading list using the classic version. Note that the text "post" is hot.

Then I switched that page to the new version and "post" is no longer hot.

Then I went back to the saved list and switched it to the new version and again accessed this shared item in case there was a version mismatch issue and the above was an unfair test. But again, I'm not able to easily get a permanent link to the post that was shared like I could with the classic version.

But the good news is that the new version fixes a photo resolution problem that the classic version introduced several weeks ago. Specifically, the classic version saved a photo with 760 x 960 resolution whereas the new version saved it with 1547 x 1955 resolution.

Facebook Lemonade: Triple-click selects too much

Another day, another problem. The hits just keep coming.

It just occurred to me that I was assuming that triple-click would work the same way in the new version as it did in the classic version. Silly me. I just did a test. I triple clicked the description of a photo in the new version and then went to the next photo. The description in the second photo WAS NOT SELECTED as it is in the classic version. So my complaint below about triple-click selecting too much content is irrelevant because Facebook broke why I would triple click in the first place!

The first screenshot shows were I triple-clicked the description of a photo.
The second screenshot shows the resulting paste into a photo caption where the "3" line had already been entered.

Note the extra white space at the top between the 3 and the text and the garbage at the bottom. The old version copied just the text, which is what I want.

The reason for triple clicking instead of sweeping the text is so that when I advance to the following photos the text will automatically be selected as shown in this screenshot.

This is what it looks like if I sweep, instead of triple-click, the text for the previous photo.